The balance between quality and speed
I used to be absolutist in this, ownership of every line of code, refactoring, the works,... but times change.
Nowadays I still do it for the important stuff, architecture, class responsibilities, encapsulation, separation of concerns, etc etc, but for example I pretty much vibecoded a debug overlay which shows stuff like draw calls, ms per function in an update pipeline etc, with the reasoning that it's technically not the product but a helper tool which touches the actual solution minimally by design(the touchpoints I was meticulous about), which doesn't have to be perfect and had to be done quick.
More recently a renderer for a robot, a single class with its moving parts, I barely looked at its code and know it's a bit messy, but i made sure the robotmanager class is good, and the interfaces/encapsulation is logical etc.
It feels like with the improvement of LLM's this is where we're headed, critical stuff getting more human oversight, and certain aspects left to test input/output, where despite it giving me the heeby jeebies I'm feeling this push and feel it makes some sense, but there's trickiness where we make judgement calls about what requires more careful scrutiny and what doesn't.
I'd almost want to have some sort of markers on code which keeps track of how much attention it has had from a human, to have a sense of how much I can trust it.
What do you guys think? Where do you draw the lines?