4 ms·
Any time I hear someone say they spent a year working on a few hundred lines of code, I have to wonder how much of the problem was other people, and how much wa
by wccrawford 16y ago
Any time I hear someone say they spent a year working on a few hundred lines of code, I have to wonder how much of the problem was other people, and how much was that person.
I suspect there's a ton of exaggeration going on here, and that's probably not the only code they worked on. It's also probably not the highest priority, either.
- dasil003 16y agoAny time? Even when the logistics of the situation are explained this clearly, and the coder is responsible for 2% of the decision making process? I really don't see where in this article there's room to chalk the dysfunction up to exaggeration or incompetence.
- dugmartin 16y agoI worked on an equivalently small feature on Longhorn/Vista and it took over 18 months for it to be completed. It also depended on shell code and it would take weeks for code to migrate up their tree and back down to us. The fun thing is that two dll's that I built for the feature ended up being standalone dlls in Windows\System32. I thought someone would merge that code into some common dll but I guess that wasn't on the schedule.
- lumisura 16y agoI'm not even going to tell you how long it took and how complex it was to replace one single icon sometimes in Vista. I worked in the Windows UX team at the time and tried really hard during Windows 7 to improve that process, because there were so many people involved and so many hours spent for such simple things. So yes, I believe what this guys is saying about his feature is possible - to swap an icon we sometimes had to track a ridiculous number of people, wait several builds to see it, and get approval from a room full of people many times several management levels above me.
- 2arrs2ells 16y agoI fought similar battles (but at a much smaller scale) trying to change some of inane dialog box text/tooltips in InfoPath for a feature I owned as a PM. I was an intern, but the pushback was rarely along the lines of "Your version isn't better" but rather "We can't handle the globalization/internationalization/testing/etc burden of making the change."
- lumisura 16y agoYup. Which is even more frustrating. Many times you got everybody to agree it would be better the way you are trying to do, but for whatever reasons that seem to be out of control of every person involved in the process, it can't be done. It's sad actually. A company full of people with the right ideas and skills that can't put those ideas in practice because the operation and processes are getting in their way.