Completing the cycle, time to revise

Been busy two months,

Shifting to banglore consumed most of the time.

Anyway that also gave me a chance to recap on few things. This time of the year usually signifies an end for my personal calendar year. So it moslty goes into doing damage control for all the things i failed at, didn't do at all or badly missed on planning in the first place. This year is not an exception.

Quick highlights :
1. I still suck at interpreted languages. Just cant get the hang of those, even though basic has a soft corner, i just simply hate them.
Same goes for object based languages.

2. I desparately failed at estimating the market shift this year, the value of my time / talent has shot up trimendously. Basically this is the cash in time for everybody, so next time you ask me for an advice keep in mind that, the last time, i sucked giving it to myself . Wasting career time has become costlier than i thougth. Damage control is on its way.

3. There is one notable and quite unexpected success though. I basically knew only the oss software development cycle and thought of others as quite tedius and theorotical to learn. Didn't think i will master them in comming years. To my surprise thats not the way it happened. Although my initial observations were correct, i had no way to know an important fact about large scale software development processes beforehand. They _all_ fail. The real benifit comes absolutely unexpectedly from the places the designers never imagined. It needs a critical mass of developers to follow the processes to have that benifit. And strikingly its very similar to the sucess of the oss development methodology. It comes from natural selection process. Although everyone pretends to follow the process on superficial level, real benifits come from getting the developers together and make them compete for resources. The processes give a common forum and act as catalysts. More details on this later.
The result was that i learned about the sdp lot quickker than i thought.