[moris_borris]

Not an answer to your question, but some perspective from my own experience.

I worked with a bunch of people like yourself at a fast-paced adtech startup. Clean code and even sustainability were not a priority, and the company had a money printer in the basement. Has the front-end gotten so messy it's unmaintainable? No problem, let's make a new one from scratch! I loved that we were given so much time to solve interesting problems with bleeding-edge tech, but I hated the filth of the code, particularly trying to read other hackers' code. And yes, so extreme was the priority of haste that these engineers were more hackers than anything else. That wasn't really my style, so I left.

Now I work with people who are the opposite. They love fussing about the `describe` blocks in their unit tests, will draw up Excel sheets to supplement the JIRA board, and spend an afternoon arguing about whether that 100% test coverage is really covering all functionality. The codebase is a textbook of how to write beautifully maintainable, readable code. Pull requests are genuinely enjoyable. But ask them to learn a technology from the last 8 years and they just start refining their refactoring tickets.

Perhaps I will find a happy medium between these two extremes.