how technology changes - my perception two years down the professional career

One joke keeps circulating about the learning of techies and their life in IT - an engineer (computer) learns maths in 1st year, C in 2nd year, Java in 3rd year, business concepts and projects in final year, and works on excel henceforth, in the IT career. Probably most of the job in IT doesn't require strong engineering skills, but strong logic and correct approach towards practical problem solving.

The same goes true for a core technical developer, I perceived. Skills are necessary, but without logic and approach, and an open mind, its nothing. I kept on normalizing databases in the initial days, the skill I learnt in my college days, to accommodate millions of entries, till I got introduced to 'lucene', and geared up to the accommodate the reverse, de-normalizing every data models into the composite flat format. No more relations, no more keys. Its time for no-SQL.

The project I worked on had three modules, quite vast and open-scoped by themselves. I wondered with awe the power of change, as I myself had to undo the modules and sieve the concepts as a part of no-SQL. The concept of code and database as separate modules, with low coupling, is fading.

I knew UI by it's definition, but only learnt with the coming of HTML5, that it can do much better than just interacting with user, analyzing logic and storing information, all in itself.

This is probably the age of aggregation. Every utility is getting bundled with features, related and unrelated, providing an one for all solution. Is it going towards good? It is too early to find out, but I am optimistic, and keep rolling like the stone with water.