4 ms·
Following this thought, it could be argued that the author did not even fix the problem, only eliminated a symptom of the underlying, serious configuration mist
by bassdigit 7y ago
Following this thought, it could be argued that the author did not even fix the problem, only eliminated a symptom of the underlying, serious configuration mistake that restricts file contents to an outdated character encoding.
- mar77i 7y agoI like your approach. And the blogpost's author does not even hint that the story told could mask an underlying issue at all. Which I find mind boggling somehow, but can we call this symptom whack-a-mole and what can be interpreted as anxiety-driven reasoning a cultural issue? Or is there a different, broader context that can wrap this up better that I'm not seeing?
- bassdigit 7y agoThe commit message succeeds in justifying the effort but lacks an in-depth understanding of the related mechanics. I can imagine the developer felt bad about 'only' committing a one character change at the end of the day and wrote the message to make up for it. Because of this un-economic outcome, he hesitated to dig deeper. There is no reason to feel bad. The cultural issue is bad management that still evaluates developers by lines of code / commit activity.