Vibecoding on ROBOCO

Vibe Coding and Security: True or False

Tue, 30 Dec 2025 10:01:21 +0900

Dohyun Jung - Principal Consultant, ROBOCO

These days, saying “I code with AI” is no longer special. It is already the new normal. Coding works — that is now a given — and today’s AI tools do far more than that in a business.

Even so, many companies hesitate at the adoption stage. The reason is always the same: security. Today I want to sort through the security concerns surrounding AI coding agents from an enterprise perspective — in particular Claude Code, the most widely chosen tool for production-level vibe coding — separating what is true from what is false.

Agentic Coding Recommendations, Explained

Tue, 17 Jun 2025 13:38:18 +0900

Dohyun Jung - Principal Consultant, ROBOCO

This post is based on Armin Ronacher’s blog article “Agentic Coding Recommendations”.

Foreword

A few days ago I came across Armin Ronacher’s blog post “Agentic Coding Recommendations” on the developer community Geek News, and it left quite an impression on me. Armin is best known as the creator of the Flask web framework, and his insights on vibe coding line up closely with the direction Roboco is heading. In this post I want to unpack the core ideas in Armin’s article in an accessible way, for people just getting started with vibe coding through tools like Claude Code, Cursor, and Windsurf.

The Art of Vibe Coding

Sun, 04 May 2025 11:59:09 -0700

Dohyun Jung - Principal Consultant, ROBOCO

Have you ever heard the term vibe coding? It didn’t start out as a compliment. It was used with a hint of sarcasm to describe developers who wrote code relying only on intuition and feel, often ignoring rigorous structure or rules. Interestingly, though, it has recently come to be associated with generating code through prompts alone using artificial intelligence (AI) — large language models (LLMs) in particular. Of course, you can write perfectly exemplary, maintainable code even when using an LLM. And if you get code that works well on the first try, without a cycle of trial and error, that means vibe coding did its job — and that you genuinely understand what AI-driven development is about.

The Traits a Developer Needs in the Vibe Coding Era

Fri, 11 Apr 2025 12:21:17 +0900

Dohyun Jung - Principal Consultant, ROBOCO

TL;DR

Even in the vibe coding era, what the best developers need at their core are fundamentals like curiosity, quality standards, and communication.
The more AI takes over implementation, the further a developer’s role shifts toward problem definition, evaluation, and accountable decision-making.
Agency matters more than intelligence, and an execution-first mindset like the Amazon Leadership Principles becomes the benchmark for collaborating with AI.

Introduction: The Traits of the Best Developers

Not long ago I came across a blog post on GeekNews by Matthias Endler, an open source maintainer and Rust consultant: “The Best Programmers I Know”. In it he lays out the traits the best developers he has worked with have in common.

Does English Work Better Than Korean for Vibe Coding?

Fri, 04 Apr 2025 08:12:04 +0900

Dohyun Jung - Principal Consultant, ROBOCO

There is one question people commonly wonder about when it comes to vibe coding, that is, developing with a large language model (LLM) like GPT: “Is there a difference in the quality of the work when I talk to the model in Korean versus English?” To give the conclusion first, in my experience and by the way LLMs work, the language itself does not change the quality of the work.

Is MCP Really Necessary for Vibe Coding? (feat. CLI)

Tue, 01 Apr 2025 10:28:00 +0900

Dohyun Jung - Principal Consultant, ROBOCO

Look around the developer community these days and you will run into plenty of talk about MCP, the Model Context Protocol. The argument goes that if we want AI to work more intelligently and more flexibly, we need an interface like MCP. And honestly, I have been watching this technical trend with real interest. Part of me looks forward to where it goes, and part of me wonders: does MCP actually have to be there right now?

Vibe Coding: Truth or Myth

Thu, 27 Mar 2025 10:18:33 +0900

Dohyun Jung - Principal Consultant, ROBOCO

I got into programming in 1986 on an Apple II — more precisely, on a “Cheonggyecheon No. 2,” a machine built from Apple OEM stock siphoned off and sold on the gray market. I have worked as a professional programmer since 1995, which means I have been coding for close to thirty years now. Over that long stretch I have lived through countless shifts in software development trends, but none as jolting as the arrival of vibe coding. Since December of last year I have been doing actual production development with vibe coding. Looking at social media lately, there seems to be a great deal of both worry and expectation around it. Drawing on my own experience, I want to talk about this new phenomenon.

The Vibe Coding Manual: A Template for AI-Assisted Development

Tue, 11 Mar 2025 06:52:53 +0900

(Version 1.0 – March 2025)

This post is a translation of the Vibe Coding Manual posted on Reddit.

TL;DR

Vibe Coding is a development approach that combines specification, rules, and oversight to build projects together with AI.
The key to a rules file is clearly separating coding style, tech stack, workflow, and communication expectations.
It applies to everything from small scripts to large applications, but you have to keep managing the AI’s scope creep and context loss.

Introduction: Core Concepts of Vibe Coding and AI

What Is Vibe Coding, and What Is It Built On?

Vibe Coding is a collaborative software development approach in which a human uses AI models (e.g., Claude 3.7, GPT-4o) to efficiently build functional projects. Introduced in “Vibe Coding Tutorial and Best Practices,” which Matthew Berman published on his YouTube channel, the concept rests on three core pillars: