Hands-on knowledge is what lets you catch things when they feel off. Anyone can spin up an app in a few minutes these days—but if you don’t really understand what the code is doing, it’s hard to know what you’ve actually built… or what it might turn into down the line.

I’m not a coder by trade. I did some light coding 20+ years ago, but that’s about it. These days, I know just enough to get myself into trouble. And if I’m being honest, I lean on the model a lot to make decisions for me. Quick reality check—it doesn’t always get it right.

What helps is having just enough context to steer things. I can go to Claude and say, “refactor this for performance” or “clean this up,” and it’ll do it. But there’s always that small pause after—did that actually improve things, or did it quietly break something else?

Thanks for sharing @Ale_Armillotta