<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Workflow on Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/ai-workflow/</link><description>Recent content in AI Workflow on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Mar 2026 18:00:00 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/ai-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Development Methodologies Compared: From Vibe Coding to SDD</title><link>http://www.heyuan110.com/posts/ai/2026-03-11-ai-development-methodologies-compared/</link><pubDate>Wed, 11 Mar 2026 18:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-03-11-ai-development-methodologies-compared/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-03-11-ai-development-methodologies-compared/cover.webp"
 alt="AI development methodologies comparison — Vibe Coding, SDD, BMAD, and pragmatic workflows"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;In early 2025, Andrej Karpathy coined &amp;ldquo;Vibe Coding&amp;rdquo; and the AI-assisted development revolution began. By Y Combinator Winter 2025, &lt;strong&gt;25% of companies had 95% of their code generated by AI&lt;/strong&gt;. But the honeymoon didn&amp;rsquo;t last — quality issues, technical debt, and project chaos forced the industry to rethink how humans and AI should collaborate on code.&lt;/p&gt;
&lt;p&gt;This article is a deep dive into the &lt;strong&gt;six major AI development methodologies&lt;/strong&gt; that emerged from this reckoning. I&amp;rsquo;ll break down what each one gets right, what it gets wrong, and — most importantly — which one you should actually use. This isn&amp;rsquo;t a surface-level overview; it&amp;rsquo;s built from hands-on experience, Martin Fowler&amp;rsquo;s team analysis, Peter Steinberger&amp;rsquo;s evolving workflow, and real production data.&lt;/p&gt;</description></item><item><title>High-Frequency Commits: Ship 100+ Commits/Day Without Chaos</title><link>http://www.heyuan110.com/posts/ai/2026-03-10-high-frequency-commits/</link><pubDate>Tue, 10 Mar 2026 18:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-03-10-high-frequency-commits/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-03-10-high-frequency-commits/cover.webp"
 alt="High-frequency commits workflow showing atomic changes flowing through CI/CD pipeline"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;AI coding tools have fundamentally changed how fast developers ship code. With assistants like &lt;a href="http://www.heyuan110.com/posts/ai/2026-02-28-claude-code-complete-guide/"&gt;Claude Code&lt;/a&gt; generating, refactoring, and testing code at machine speed, many teams now produce &lt;strong&gt;50 to 150 commits per day&lt;/strong&gt; — and that number keeps climbing.&lt;/p&gt;
&lt;p&gt;But here is the uncomfortable question: when commit frequency skyrockets, why do some projects accelerate while others descend into chaos?&lt;/p&gt;</description></item><item><title>Tmux Complete Guide: From Basics to AI-Powered Multi-Agent Workflows</title><link>http://www.heyuan110.com/posts/ai/2026-03-03-tmux-guide-ai-development/</link><pubDate>Tue, 03 Mar 2026 10:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-03-03-tmux-guide-ai-development/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-03-03-tmux-guide-ai-development/cover.webp"
 alt="Tmux terminal multiplexer for AI development workflows"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;If you work in the terminal, you&amp;rsquo;ve probably lost an SSH session during a long-running task. Or struggled to juggle multiple terminal windows while debugging. Or watched helplessly as Claude Code&amp;rsquo;s conversation vanished when your laptop went to sleep.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Tmux solves all of these problems&lt;/strong&gt; — and in the age of AI-powered development, it has become arguably the most important terminal tool you can learn.&lt;/p&gt;</description></item><item><title>AI Workflow Playbook: From Prompts to Production Code</title><link>http://www.heyuan110.com/posts/ai/2026-01-30-ai-workflow-real-guide/</link><pubDate>Fri, 30 Jan 2026 10:00:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-01-30-ai-workflow-real-guide/</guid><description>&lt;p&gt;Most people have been using AI for months, yet they&amp;rsquo;re still stuck in &amp;ldquo;ask a question, get an answer&amp;rdquo; mode. They&amp;rsquo;ve had plenty of conversations with ChatGPT, but when it comes to real work, the results always feel lacking — answers are too generic, generated code won&amp;rsquo;t run, or the output screams &amp;ldquo;written by AI.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The problem isn&amp;rsquo;t that AI is bad. It&amp;rsquo;s that &lt;strong&gt;we&amp;rsquo;re using it wrong&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This article is a practical AI workflow methodology distilled from real-world experience — covering how to ask better questions, how to write effective prompts, how to use AI for programming, and how to deploy AI in enterprise settings. If you&amp;rsquo;re still figuring out how to make AI genuinely useful, this guide is for you.&lt;/p&gt;</description></item></channel></rss>