Re:Symptoms of rotting design
by marcus on Wednesday January 28, 2009 @11:23AM
(#453963)
Actually that is what separates the professional from the hobbyist (I've seen both bad professional programmers aka 9-5ers and amazing hobbyists), and when I work professionally both in my startup and in a previous life as an employee I put on my waders and jump right into the thick smelly bog. But especially when you take a couple of years of vacation and work for fun on projects that interest you, you find out that sense of ickiness is probably the best indicator of code rot.
[ Parent
| on HN ]
Re:Symptoms of rotting design
by LogicHoleFlaw on Wednesday January 28, 2009 @11:45AM
(#453996)
One skill that I'm growing to appreciate as I become more experienced is the ability to find a problem and determine if the best action is to do a minimally invasive change, a workaround, or a full restructuring. I don't always make the right call but I'm getting better at it.