You can generate code without understanding it, but you can't generate judgment, taste, or the kind of long-term thinking that prevents technical debt from metastasizing.
Those come from giving a shit about the work itself, not just shipping it.
Readit Newsashutosh-mishra commented on I know when you're vibe coding alexkondov.com/i-know-whe... · Posted by u/thunderbong
ashutosh-mishra commented on Attention is your scarcest resource (2020) benkuhn.net/attention/... · Posted by u/jxmorris12
This connects to a broader truth about knowledge work: we often treat focus as a personal failing when it's really a design problem.
Most people try to fix their focus through better time management or productivity systems, but the real solution is usually structural - changing what you're responsible for, not how you manage those responsibilities.
ashutosh-mishra commented on So you're a manager now scottkosman.com/post/blog... · Posted by u/mooreds
The real mindfuck is that everything that made you successful as an IC - being the person with answers, moving fast, shipping stuff - can actually make you a worse manager if you're not careful.
Your new job is to make other people successful, which sometimes means slowing down, asking questions instead of giving answers, and being okay with solutions that aren't exactly what you would have built.
The fact that you're accounting for invisible elements and accidental shadows shows deep domain expertise.
This is exactly the kind of thing general-purpose tools miss because they assume clean inputs.