


I help dev teams be insanely productive with AI. Consulting: coryhouse.dev


Nah. My opinion is the value of my coding skills is trending towards zero.
Wow what an amazing coincidence, not a single one of your opinions poses a risk to your personal social status

No, I want *your* input. I can ask AI for its opinion myself.
I want you to visit me. But I equally want you to walk there.

I agree with this. But, many teams aren’t mature enough to eliminate human reviews yet. They need better automated checks first.
If you haven’t yet built a system for shipping to prod without human code review, then…with love…maybe software isn’t the thing for you.

Because the teams’ automated guardrails and AI review process isn’t good enough yet
Why would you want a human to review your code? Genuinely asking

Sure, the reviewer may use AI to assist their review, but if they do, they must type any comments in their own words. This proves they understand the point made and avoids verbose comments. And since typing a comment from scratch is extra work, this rule helps avoid "nit" comments.

If I ask a human for a review, I want a human’s input. If I want an AI’s input, I’ll just run it myself. So, here’s a team rule we just implemented: “If you’re asked to do a code review, you must do a human review.” No AI comments allowed.

In high functioning orgs this was a reality before AI. Now that AI is here, it’s becoming table stakes. Developers need to step up. Stop merely taking orders. Set the vision and execute it.
At my company, devs come up with almost all of the tickets and we don't really have this problem. The PO is basically just there to help make sure we're moving in the right direction and give us an easier way to reach out to users. Devs really need a product mindset these days.

Problem I keep seeing: Teams with one product owner making tickets for 3-10 developers. This doesn’t work anymore. In the age of coding agents, one PO can’t create tickets fast enough to keep developers busy. Code isn’t the bottleneck. Requirements are. Reorgs are coming.

AI is blurring roles. Developers are operating as product owners. Product owners are doing development. QA is generating automated tests. Prediction: These roles will unify into a “Product Engineer” role that owns the entire app (or a vertical slice of a large app).

True. If a process *must* be deterministic, then skills are the wrong answer. Write code instead.
I like skills but relying on the markdown ones to get deterministic results isn’t ideal

Skills are like functions. They do something specific. They accept arguments. They can have one or more outputs. I can invoke them or schedule them. They’re composable (skills can call other skills). I can share them with my team, my company, or the world.

Fascinating claim. My concern: Building software without tickets works fine for a solo dev. But with multiple devs, tickets help us avoid conflicting or duplicating work. How can multiple people work using a mere spec without chaos? Is verbal coordination sufficient?
Any AI SDLC workflow which involves taking a spec and turning it into a backlog of issues or tickets is a dead end. There is only the spec. Any materialization of the spec into discrete units of work can only introduce drift. It is waste.

I’d love to buy this as my son’s first car and then use it for my whole family. It could drop my kids off at school, drive itself home to pick me up for the gym, and rent itself when we’re not using it. And it drops us off and parks itself! So eager for this to go mainstream
Select customers are now being invited to purchase Cybercab for personal use

Nearly every process in the SDLC warrants a custom skill: /create-ticket /fix-bug /implement-ticket /review-code /open-pr /fix-pr-comments If our team repeats a process, a skill means we can standardize, automate, and continually improve the process.

Lazy reviewer in 2024: “Looks good to me.” Lazy reviewer in 2026: “Here’s 2 things Claude found.”