3 ms·
Agreed. I love cleaning out warts, fixing broken APIs and removing unneeded code. I love looking at the output at "git diff --staged" seeing lots and lots of re
by pilif 14y ago
Agreed. I love cleaning out warts, fixing broken APIs and removing unneeded code. I love looking at the output at "git diff --staged" seeing lots and lots of red and very little green.
But that's just me - any maybe other developers in my team. For everybody else - marketing, sales, customers, end users - this is completely irrelevant. Nobody really understands this kind of work, much less actually sees a value in it.
Adding a blinking logo somewhere and you're the hero of the day. Exchanging 500 lines of bad spaghetti with 20 lines of beautiful art and you're wasting everybody's time.
But because I love this kind of work so much, I don't care. I'm in a position where I can do such things for fun an pleasure, so I'm doing them.
- coderintherye 14y agoI like it, because I seem to have a knack for it and mostly because I enjoy working on things that no one else wants to touch. It's nice to have a degree of autonomy and not have to deal with working on a big team, even if it means not getting to work on new things.
- ams6110 14y agoFor everybody else - marketing, sales, customers, end users - this is completely irrelevant I get satisfaction out of making code better too. But your observation is important. Customers, who are ultimately paying your salary, don't care about what language you use, what design patterns, what version control system, whether you used a key/value data store or an rdbms, or whether the implementation is object-oriented, functional, or spaghetti, or any of the other things geeks like to masturbate over. Customers care about: does the software solve my problems, and is it (reasonably) easy to use. If you lose sight of that, all your technical improvement work will come to naught.