Hacker News Reader

It's not a programming advice. Similar counsel is dispensed in various tech, and non-tech fields, because it's about relations with other people which sometimes could be more important than efficiency for one's career, or comfort. However, to discourage from thinking about improving other programmers code, and call it "the best programming advice"? No way.

View on HN

I've never worked in a software only organization. But instead in smaller teams of specialists. Usually there is an process where if you have an issue with something you work with the person who's responsible to fix it. You just do not go in and change things. You never go in and change things without telling them.

Friend of mine talking about how he fixes bugs. Most of the time he tries to figure out where the problem is and and then writes that up. Then uses blame to figure out who wrote the code and reassigns the bug to them.

Him: I Eddy, hey think there is a problem with this condition in this function.

15 minutes passes

Eddy: checks in bug fix closes ticket

You didn't read to the end. The author recognizes this as patently bad advice, and was glad to have received it so he was conscious of what not to do.

Yup, my fault. I exploded too quickly, probably because recently had a similar discussion related to my own work.

Reply on news.ycombinator.com