|Posted by Bill on February 15, 2010 at 1:31 AM||comments (0)|
A coworker of mine posted the following on Twitter... and I just had to respond, and since the link site didn't allow for a response I added it to here:
@DDame Debate continues: Split development and maintenance teams? Or have a single project team? http://bit.ly/azwu0r
Here is my response:
You are soooo right. Devs really need to "eat their own dogfood" in order to become better devs. It's amazing how fast they get better when they actually have to run that software as well. When they discover that nothing useful is put into the logs until it's put into Debug mode, they figure out that a 2am call will not get fixed by 2:10am unless they put some thought into it while they code it the first time.
All Devs need to walk a day in their users life to ensure that the decisions they make are ones that will last and not just band-aids that fall off very quickly.
I've said it in the past, and I'll say it again: If you aren't forced to maintain your own software you are only half trained, and are guaranteed to only create half-assed solutions.