4 ms·
Not OP, but I read the "antagonistic" style of the post as just the usual catharsis humor. All in-jest. I've used that style of writing plenty before. It's a
by fpgaminer 5y ago
Not OP, but I read the "antagonistic" style of the post as just the usual catharsis humor. All in-jest. I've used that style of writing plenty before. It's a good way to blow off the steam of working with these rather absurd, archaic systems that we have to tackle on a daily basis. Programming can feel a bit kafkaesque at times, so a bit of aggressive/dark humor goes a long way.
But I do agree, it felt too thick. Still a very interesting topic regardless.
- hn_throwaway_99 5y agoThe problem I see is that I often see this type of detached, "wow, look at all of these previous shitty decisions!" attitude inject itself, completely unnecessarily, into the workplace. I've actually made it something I won't compromise on: I refuse to hire people who I suspect will have this attitude. It's one thing to express frustration at previous decisions that make current work more difficult. However, when I see that morph into an arrogance of "how could people have made such a stupid decision" (especially when some of those "people" may still work at the company), without even trying to understand the context of why that decision was made in the first place, it shows to me that person is not an engineer I want to work with.
- QuercusMax 5y agoOn one team, we had a lot of code that had been written hastily because we were OK with taking on technical debt in order to move more quickly. We'd reconsider old design decisions and blame "old $me". It was all done in good fun, and I was happy to take the blame as senior engineer.