4 ms·
I love how he characterizes what developers do as "just writing code" -- the whole article is basically a whinge: don't make me do ops, don't make me write test
by workinfunk 8y ago
I love how he characterizes what developers do as "just writing code" -- the whole article is basically a whinge: don't make me do ops, don't make me write tests, don't make me think about the problem, don't make me re-use existing solutions, don't make me pick the right tool for the job, don't make me use sustainable processes -- I just wanna "write code". Code is basically the poop that results after you digest the problem. The best code is as little code as possible, but this guy just wants to make code poop for a living. Sorry guy. Time to grow up.
- deleted 8y ago[deleted]
- dlandis 8y agoThe author also seems to be oblivious to the fact that many developers actually _enjoy_ doing those other things (besides just cranking out code).
- mmt 8y ago> Code is basically the poop that results after you digest the problem. The best code is as little code as possible This is, perhaps, one of the best metaphors I've read for explaining this concept. As someone who does one of the "lower" jobs, I rankled at his "hierarchy" of roles notion. Never mind that I probably could write application code if so inclined (and do routinely write "infrastructure" code and sometimes have had to fix those developers' code in production). I occasionally like to point out to "engineering" or "technology" [1] managers that not all problems can be (or are best) solved with software/code. Some of use, when we digest a problem, can poop out zero or even negative code. [1] In quotes because they're nearly always actually only software engineering or technology managers.
- jiveturkey 8y agoMy new favorite aphorism! My previous favorite: Linux is free as in free mattress.