3 ms·
> or at least no good one Understanding whether the purpose was good implies understanding the purpose. Even with very bad code you can at least see what the a
by chucksmash 5y ago
> or at least no good one
Understanding whether the purpose was good implies understanding the purpose. Even with very bad code you can at least see what the author was going for. Most code I've seen and felt was bad could be described as "Author needed to do X but wasn't aware of Y." I can't remember a time where I had to deal with code where I couldn't figure out what X was.
- emodendroket 5y agoIt becomes pretty apparent to me, often, that the author wanted to put something on their resume, or wished to spice up a boring task.
- a4isms 5y agoYou keep saying this is your lived experience, and a lot of other people are saying that it is too rare to be worth making a presumption without putting in the work to go look. What I’ll say to you now is that if you are actually looking for the reasons, and all you can find are people making your life hard for the glorification of their ego, you have a much bigger problem than whether it’s worth presuming that there is no reason for code you want to remove: You are located in a local pessimum. Consider working on a different code base. Ask yourself what is going on that you keep running into all this code written by people you disrespect so much.
- emodendroket 5y agoIt happens to me infrequently now and I work with a team I really respect. But it took me the better part of a decade to land there.
- a4isms 5y agoOur experiences and outlook may differ, but I am very gratified to hear that you have found your way to a better place.