[whoomp12342]

I get it, but as a senior member of the team you have to be careful. Yes it is fun to get shit done really fast, yes it creates short term value but you have to be aware of the downstream effects. When you build new stuff, set patterns, create infra, you are setting the example that junior members will learn from at best, and copy/paste at worst. Do you want a ball of mud because its all too easy to get one

[wreath]

I think what you're talking about is not only shitty code but also poor design which is far more dangerous. Writing shitty code behind good design is a different story, and to my understanding, this is what the author describes.