Want to get into the top 10% of your engineering team by leveraging agentic engineering workflows? I'm planning a 2 day workshop here: https://form.typeform.com/to/EDuBEz4UI shipped a feature with AI in record time.Then I actually read the code.60+ files. Weird abstractions. Tests that technically passed but proved almost nothing. Components rebuilt from scratch for no good reason. What looked like a finished feature was probably 70–80% of the way there.And the worst part? This wasn’t my first time doing this.I’ve also sat in a code review as a senior engineer and realized I couldn’t properly explain code that “I” had just written.I use Claude and Codex constantly. I’m not going back to hand-writing everything. But after using AI to build software at startups, inside my own business, and on large production systems, I think we’re learning the wrong lesson from how fast these tools can code.The question isn’t whether AI can write the code.It’s how much you need to understand before you’re willing to ship it.
I'm opening 12 spots for a weekend workshop in October for devs who want to ship quality software with agents.Sign up here: https://form.typeform.com/to/EDuBEz4U"You're absolutely right, I should have caught that"I'm one of the top 10% of AI users in a 1,000-person engineering org this year. I'm not an AI hater, I ship with these tools daily and I think they're genuinely fun to use. But I've also watched "customers don't care about the code" turn into an excuse for engineers to stop thinking entirely, and that's how you end up with 5,000 lines nobody can explain, a catastrophic bug in prod, and Claude cheerfully saying on the way down.Let's explore ways to maintain quality software without becoming a "meat proxy"
Become an AI Engineer at parsity.ioI recruit for AI roles on the side and I pulled real, live forward-deployed engineer postings and broke down exactly what they're screening for. Turns out it's not what most "learn AI" content tells you.What's actually in these postings:Real applied AI experience: shipped production agents, not tutorial chatbotsRAG, retrieval quality, evals, and agent-to-agent communicationSurprisingly low years-of-experience requirements compared to typical senior rolesThe ability to explain technical tradeoffs to non-technical stakeholdersVoice AI showing up more and more as a differentiator — mentioned in this episode: AI Voice Pioneers (https://www.skool.com/pioneers) and Retell AI (https://www.retellai.com)Degrees mattering a lot less than you'd think, at least in the Bay AreaWant to actually build one of these skills instead of just reading about it? Free RAG project: parsity.io/ai-with-ragIf you're trying to reverse-engineer your way into one of these roles, this is what the actual postings are telling you to build toward.
We teach AI systems engineering at Parsity: parsity.ioIn this one I get into why senior is mostly a comp band with a name on it, the three things every senior actually needs to know/have, the big fish / small pond strategy I've been running for seven years, and the single move that gets you promoted faster than getting better at your language.Also: why you should stop replaying that interview where somebody corrected you.
Become an AI engineer in 45 days. Join Parsity: https://parsity.ioBeing a "coder" is getting less and less about coding. I've been writing code for 12 years and I'm watching skills I worked hard for get automated.Counter-intuitively, I believe a new brand of software developer is going to be even more valuable and in demand going forward.Your existing skills aren't disappearing but the ones that matter the most certainly are.Book a call with me here: https://calendly.com/brianjenney83/15-minute-meeting-your-web-dev-roadmap-clone