Behind green bars
November 13th, 2009
Another day of coding is over and you produced some beautiful code. Now what? Do you know exactly how long it will take until that brand-new feature gets to its intended user? A week? A month? Never?
It’s a shame that most code produced out there will park for all that time until is released. Maybe that was normal when it would take days just to compile the whole system. But today, even with all the processing power and automation, new releases are always delayed by deadlines, testing stages, approvals, sign-offs or any other form of bureaucracy.
If the code is really good it shouldn’t have to wait. Maybe it’s time for programmers to stop hiding behind the green bars of their builds and start pushing their code out of the door.
If the code is really good it shouldn’t have to wait.
How would you know if the code is really good to the intended user? You might code, but you cannot represent the users and claim that what you think is good code/feature may not be same as what the user thinks it to be. As developers and testers, We should not represent the customers/end users because what we think may work best for them may not be necessarily true.
Happy Coding,
Parimala Shankaraiah
@Parimala Shankaraiah
In my view, working best for the user is one of the characteristics of good code. I never claimed that it can be achieved without collaboration. Instead, what I’m saying is that after it’s built, it should be available as soon as possible. Otherwise where would be the beauty on it?