My answer for the weakest link in software development today is the estimation, and for various reasons. Most of the times the people who estimate and people who develop are different, their skillsets are different, and most importantly the business needs and constraints change at a higher frequency. Of course we know this, that is why agile development has flourished. [Continue]
For quite some time I have been trying to digest and slowly apply Theory Of Constraints in what I do. Like Jack Vinson says, Necessary But Not Sufficient is a great book to get encouraged about it. I too was drawn in by the same book. [Continue]
I have been reading about REST a lot recently, and hence about architectural styles. Perhaps I have found them in the opposite order. Nevertheless, it has been extremely refreshing and educative. [Continue]
Matt Assay points to a study which says that 62% of IT projects fail. The study cites two primary reasons: Managers do not consider the time and effort required to transfer of the know-how from designers to developers. QA is not given enough importance, and hence time. [Continue]
Kent Beck says that XP is in the danger of getting stagnated because of a combination of limited adoption and no opposition. It has become like the standards, which everyone accepts in principle, but no on adopts in practice. I like XP, it was like a breath of fresh air after working through various waterfall models and burning the hands. [Continue]
ocean has a radical perspective about what software development is, and a good one too. … Given all this commuication going on it may be that creating software is actually a communication exercise. The goal of this communication exercise isn’t to create code — or anything else. [Continue]
Somehow a lot of software professionals believe that my Mom will read this code. Or at least they want me to document it such that even she could read it. Why don’t they see the problems? [Continue]
This is what I tell my non-technical friends who end up being associated with either buying or using a new piece of software. What usually happens is that most of them get over-zealous, either because of the sophistication of the software systems or because of the enthusiasm about the trend and they completely miss the fact that the software is for a purpose. Rather, the software is supposed to solve a problem for them. [Continue]
A friend asked me if software was a good profession to work once and earn forever. He said people like Bill Gates inspired him to build such a model. I thought it was an unique aspect to consider to decide whether he wanted to get into the software domain or not. [Continue]
Which is the must-have skill required to become a software developer? Good question, I seem to be getting a lot of questions nowadays for which I have only personal answers. Anyway, I personally think it is a problem solving approach. [Continue]