26 ms·

Writing code every as a CEO now and again is a nice thing to say but it isn't a scalable approach if you want to maintain that code properly. You can't just exp

• quanticle 15y ago
  Why not? Of course you can't have the CTO drop everything when there's an unexpected bug, but I do think there is value in coding, even for "upper" management. Even looking in on the code from time to time can give you a snapshot of where the product is at and in which direction it is evolving. If that direction is different from what you expected, you can ask the programmers why they chose to use the approach they did. I think the most important thing is that the CTO does not place his or her code above the code of the individual maintenance programmer. The worst thing he or she can do is somehow mark his or her code as "untouchable". Untouchable code is bad code, regardless of how well it works or how well it's written. It doesn't adapt to changing requirements like the rest of the application, and the rest of the application has to go out of its way to accommodate it. However, as long as he or she makes it perfectly clear that his or her code is just as subject to change and modification as everyone else's, I don't see why the CEO/CTO can't get their hands dirty now and again.
• MatthewPhillips 15y ago
  Why wouldn't someone else fix the bug?