“Now little by little I'm getting calls where it's like, we kind of vibe coded this, but maybe we should treat it more like a prototype. Can you take what we vibe coded and refactor it into something more enterprise quality and maintainable? … It's a really good idea to do some heavy architecture work up front and then let Claude help you out.”

I think you're definitely on the right track. I mean, from the vendor side here at the Mad Botter, it's funny. Most of the year was kind of a lot of people like, well, we can just vibe code this up internally, right? And now, little by little, I'm getting calls where it's like, hey, we kind of vibe coded this, but maybe we should treat it more like a prototype. And can you build us an actual system or take what we vibe coded and fix it to be simple, but kind of refactor it into something more enterprise quality and maintainable. The other thing I've been noticing is I think you're right on the core fundamentals education-wise. Because, you know, of course, I work a lot with Claw Claude. I think if you're not using these tools, you're kind of falling behind, at least from a commercial standpoint. But you really need to know your architecture. I'm talking about your, you know, your, your big old book, your canoe. You need to know your canoe. Or else, I mean, Claude, and I'm not just picking on Claude, right? So Codex, whatever, will just slap together crazy stuff sometimes that's totally inefficient, totally insecure. Not to…