https://roboco.io/en/tags/engineering-management/ Recent content in Engineering-Management on ROBOCO Hugo en-us Thu, 26 Mar 2026 17:26:21 +0900 https://roboco.io/en/posts/vibe-coding-rules-vs-taste/ Thu, 26 Mar 2026 17:26:21 +0900 https://roboco.io/en/posts/vibe-coding-rules-vs-taste/ <blockquote> <p>The job of AGENTS.md is not to clone your developers. It is to pin down only the boundaries where accidents must be prevented.</p> </blockquote> <figure><img src="https://roboco.io/posts/images/Dohyun.png"><figcaption> <h4>Dohyun Jung - Principal Consultant, ROBOCO</h4> </figcaption> </figure> <p>Teams that adopt vibe coding soon run into a similar question. Once you start putting an <code>AGENTS.md</code> or <code>CLAUDE.md</code> in every repository to tell AI agents the rules, it becomes murky how far you should pin things down as shared rules and where you should leave things to individual taste. Draw that line wrong and two problems appear at once: the safety rules that absolutely must hold get loose, while choices that are really just preferences become needlessly rigid.</p> https://roboco.io/en/posts/organizational-design-for-vibe-coding/ Fri, 20 Mar 2026 21:23:40 +0900 https://roboco.io/en/posts/organizational-design-for-vibe-coding/ <blockquote> <p>Whether vibe coding succeeds or fails comes down to organizational design: whether the team can verify and ship AI-generated changes in a repeatable, safe way.</p> </blockquote> <figure><img src="https://roboco.io/posts/images/Dohyun.png"><figcaption> <h4>Dohyun Jung - Principal Consultant, ROBOCO</h4> </figcaption> </figure> <p>Many organizations understand vibe coding as little more than &ldquo;a way for developers to produce code faster.&rdquo; So the adoption conversation usually starts with tooling. But what actually decides success or failure in the field is organizational structure, not the tool or the model&rsquo;s performance.</p>