Productivity on ROBOCO

The Best Production-Grade, Cost-Effective Vibe Coding Tool from an Enterprise and Heavy-User Perspective (as of January 2026)

Sun, 25 Jan 2026 11:45:52 +0900

This piece was written as of January 2026. Pricing, usage limits, context windows, and plan structures change extremely fast, so I recommend reading it for the “principles and structure” rather than the specifics.

Dohyun Jung - Principal Consultant, ROBOCO

Vibe coding tools are entering the phase where “whatever you use, it more or less works.” So for enterprise users and heavy users, the question naturally shifts. It is no longer “which tool is the smartest,” but which tool you can use every day in production without hitting a bottleneck, at a cost that still makes sense.

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.

Drawing Architecture Diagrams with AI

Sat, 14 Jun 2025 12:35:06 +0900

Dohyun Jung - Principal Consultant, ROBOCO

When people do vibe coding, they often assume the code alone is enough. Reality says otherwise. Code without documentation is like setting off on a trip without a map. If nobody knows where the destination is or what the route looks like, nobody will come along. Documentation matters especially in vibe coding because code isn’t merely there to run — it exists to convey your ideas and design intent accurately to other people. Documentation smooths collaboration, clarifies where a project is headed, and ultimately forms the foundation of a sustainable development environment.

A Review Strategy for Vibe Coding

Sat, 07 Jun 2025 12:21:04 +0900

Dohyun Jung - Principal Consultant, ROBOCO

It is true that adopting vibe coding automates several areas of development and raises productivity. But review is something people have to do, because people are the ones accountable for the outcome — and so the bottleneck ends up moving to review (document review, plan review, code review, and so on). Today I want to talk about review.

TL;DR

Vibe coding speeds up generation, but if code, document, and plan reviews stay the same, the bottleneck simply shifts to the review stage.
To raise review quality, make approval accountability explicit, and use checklists and risk flags so that reviewers judge actively rather than passively.
The more automation grows, the more deliberately human review has to be designed — you need a structure that attaches meaning and accountability even to small actions.

Let’s start with code review.

The Vibe Coding Productivity Equation

Wed, 21 May 2025 08:56:24 +0900

Dohyun Jung - Principal Consultant, ROBOCO

I often get this question from developers: “This is how I develop — does that count as vibe coding?” It leaves me rather baffled. Why are Koreans in particular so fond of measuring themselves against a standard, almost like religious fundamentalists? What matters is not whether you are doing vibe coding correctly, but how much vibe coding actually improves your productivity.

There is another question I hear often: “Can you really do vibe coding without knowing any programming at all?” That is exactly what I want to talk about today.