Archive for the ‘Development’ Category
Your top priority is just another errand for others
Posted by: Manas in Development, Misc on January 29th, 2009
Finishing any sizable work always takes more time than expected, more than estimated, more than it should. Why?
Because for every work that you do, you have external dependencies. There are small bits of things that need to be done by others for you to complete your work. And those small bits of work are as important for the whole work as the big chunks are. Just as a small needle in a sewing machine is as important as the big motor driving the machine.
And those small bits of work need to be done by others. And even though these small things hold the highest priority for you, for others, it may be just a side thing; an errand to be run once in a while or when there is a mood.
And surprisingly, there are just too many of these small bits of work in any sizable amount of work. And unsurprisingly, because of their size (or rather lack of it), these bits are never visible when you make your grand plan. When you make the grand plan, you see big things and budget for them. But small things? Because they are invisible, they won’t be budgeted for. And they’ll take longer to finish because of external dependencies! After all, your highest priority item is just another errand for others
Caught ya!
Anyway, there is no point in holding a magnifying glass and looking for small bits when estimating time. It’s too much of effort and you won’t be able to do it anyways (remember, these are too small to be seen when your mind is occupied with big items).
Just go by the rule of thumb - it takes twice the time, twice the money and will give you half the returns than what you expect.
Evolution of a Programmer
Posted by: Manas in Development on December 5th, 2008
There is a usual evolution of a programmer story popular on the web. There is another one, however, given by Vishal. Here it follows -
A programmer, in fact any techie, goes through three phases of evolution:
1. Jackie Chan - You are young, smart and energetic. Even though you can fight, you mostly dread the enemy (mostly the powerful ones). Your fights tend to go on longer and you are mostly beaten up by the enemy. Only towards the end, do you get a control on the situation. You don’t use any sophisticated tools for fighting, you do it mostly with hands OR whatever you can lay your hands on (including broom).
2. Bruce Willis - You have developed a passion for fighting now. You have learned to use tools that boost your productivity by killing enemies faster. Also, you keep a tight control over the enemy right from the begining. But you still can’t do it without getting hurt. You are so involved in fighting that you have blood running down your face and you run bare-foot on glass pieces.
3. James Bond - This is what you eventually become. Calm, fast and effortless. You have equipped yourself with an array of extremely sophisticated tools. With these tools, you can not only kill scores of people by just turning the cap of your pen, you also know how to keep yourself unhurt. Finishing a task is just a cinch for you. And by the way, you have also learnt to indulge in non-technological pleasures
Politics Oriented Software Development
Posted by: Manas in Development on December 5th, 2008
Politics Oriented Software Development paints a clear picture of how political forces play in software development and how people can consciously jeopardize a product even though they may be directly involved in its development.
If you haven’t read it yet, it’s high time you read it. Time and again, I have been reminded of the truthfulness in this article. Even though the article mentions software development, it’s true for every industry where the work is done as projects.
Whether a Startup or a large company, most people always put short term personal gains (which includes ego boost) over long term project viability. The sooner we understand and accept it, the better it is.
Isn’t there any hope? Well, no and yes. No because people will not change. Yes because now that you know how software development really works, you can figure out what kind of influence will work and what kind will not work.


RSS