News for hackers. Stuff that matters.
Re:John Carmack on Inlined Code (2014) by C4stor on Tuesday January 22, 2019 @05:48AM (#18967385)
The ops team care. When they'll want you to switch to another logging output config, you'll answer one hour later saying "done". Two days later, you'll fix another two or three of those config. One week later, you'll fix the final one.

It's annoying to everyone.

If it's not config, it's library versions, it's a change in a "boilerplate" argument, ...

Code duplication makes it hard to update all the code that should be "the same". Everyone involved in actually having code updated every now and then cares about it.

Re:John Carmack on Inlined Code (2014) by SuddsMcDuff on Tuesday January 22, 2019 @05:51AM (#18967397)
Rate of change of a particular piece of code is a factor too, given. In my experience logging boilerplate has a very low rate of change, so I figured it was a good example, but I guess everyones experience is different.