🚀 Exciting Update from the Roxas Project! 🚀
We are pleased to announce a significant development milestone with the recent commit (6c2f572) to our combined test branch. This update, spearheaded b
We're speedrunning software development processes with Agents. People started with a PRD (waterfall), but now we're moving on to smaller, more iterative and testable chunks of work (agile).
there isn't going to be "one best agent / model" to rule them all. I think we need to build frameworks that use all of them, so we don't care which one is "best"
who is using all of the agentic CLI tools, all of the time?
If Vibe Coding is breaking production, it’s not the vibe coding nor the people that you should be worried about. It’s your process / CICD / testing that is the issue.
I think the key insight from Gene Kim and Steve Yegge in their Vibe Coding book is that we need to treat Agents like junior engineers. It follows that all of the systems and processes around software development should be scrutinized and applied to a much higher degree.
Reading what Claude Code is planning on doing surfaces design decisions that it's making implicitly. Can't take your eye off the ball.
"The MCP is a Lie!" - Episode 3 of Enterprise Vibe Code is up! www.youtube.com/live/Jry1YUT...
To merge my two worlds: "DevOps Discipline Equals Freedom". If you have the utmost confidence in your CI/CD process, then you can trust virtually anything an Agent produces while Vibe Coding.
I have a theory that if you invest time up front building your guardrails (AGENTS.md, CI/CD, Github branch protections, etc) instead of features, you can go much faster later with much more parallelism because you can treat each Agent like a member of your software development team.
Vibe Coding done right should feel like a Choose Your Own Adventure game.
Vibe Coding with agent constraints set up correctly is like panning for gold, except the gold are problems/decision points to use your technical knowledge.
Invest in the paid agentic coding tool. Challenge yourself to get the nicer-than-you-need version.
Dialed infrastructure means dialed agents.
Second episode of Enterprise Vibe Code is up! We install a couple MCP servers and move our website over to www.enterprisevibecode.com
www.youtube.com/live/3BWPfrg...
What do you do while your Agents are doing work? I'm writing these.
Gene Kim and Steve Yegge said it best that when Vibe Coding, burning tokens is learning. The more you spend, the more you learn how to use the tokens more effectively. It follows that, unfortunately, how good you get at this is how big your budget is.
I paid the $100 for Claude Code Max subscription and I only got to 38% usage in my first session where I used it for nearly the entire time. Sounds like I'm gonna have to spin up some parallel agents.
Dialing in your Agent's PR and CI/CD workflow for your project enables parallelism as if you had a team of developers working for you.
Half of your job as a software developer is to write code. The other half is to tell people about it.
your AI Agent should be watching your CI/CD build and iterating on it to make it pass.
We caught Claude Code red-handed a couple times and gave it corrections to pursue a better path.
It was fun to have a nice tidy project start and finish with no editing or hand waving required.
I just released my first "Enterprise Vibe Code" livestream episode! I created a super basic Github Static Page site to illustrate my Agentic AI workflow with TDD, CI/CD, and Github branch protection rules.
youtu.be/RjQEhASdKW0
woot!
I’m planning on building an enterprise-grade app end to end in public, open source, on livestream, over time. Who wants to watch?
In Extreme Ownership, one of the principles is "There are no bad teams, only bad leaders". Vibe Coding AI Agents can only perform as well as you lead them. You cannot blame them for bad output.
I think DevOps has an unfair advantage in Vibe Coding because our entire jobs are about enforcing the Software Development process. We just now have to enforce it on Agents to ensure their outputs are acceptable.
TDD is a must for Vibe Coding. So is CI/CD.
I see this in Jiu-Jitsu with recording rolls. Hopefully I can fix that for at least one class of problems with my new Vibe Coding project, Roxas.
Gary Vee's "document, don't create" advice should be automated as much as possible. I think we do so many little cool things every day that the value just evaporates as soon as we do them and don't talk about them.
