One of the most common questions I expect to get about this blog is: “How do you write in English so well if you are Korean?” The answer is simple — I do not write in English. I write in Korean. Claude writes in English.
But it is not as simple as hitting a translate button. There is a real workflow here, and I think it is worth showing in detail because it is one of the most practical applications of vibe coding I have found so far.
The Old Way I Would Have Done This
Before AI, if I wanted to write a blog in English, I had a few options:
- Write in English myself — possible, but slow and awkward. My English is decent for conversation and code reviews, but writing a natural-sounding blog post is a completely different skill.
- Write in Korean and use Google Translate — technically works, but the output reads like… Google Translate. Stiff, unnatural, sometimes hilariously wrong.
- Write in Korean and hire a translator — expensive, slow turnaround, and hard to find someone who understands tech topics.
- Just write in Korean — limits my audience to 50 million people instead of billions.
None of these options were great. So for years, the idea of an English blog stayed in the “someday” pile.
What I Actually Do Now
Let me walk you through what happened with the previous post about vibe coding. This is the actual process, not a simplified version.
Step 1: I tell Claude what to write, in Korean.
I said something like: “Write a post explaining what vibe coding is. Use my actual blog as examples. And I want to address the criticism that it is not real coding.” That is the entire brief. No outline, no bullet points, no draft. Just a few sentences describing what I want.
Step 2: Claude writes the first draft in English.
This happens in about 30 seconds. Claude produces a full article — headings, paragraphs, examples, the works. The first draft is usually decent but feels a bit too polished, too “AI-perfect.”
Step 3: I give feedback, still in Korean.
This is the part that makes the biggest difference. I read the draft and say things like:
- “This sounds too stiff. Make it more like how a real person would explain this to a friend.”
- “Add the part where I actually asked you whether vibe coding is legit.”
- “The section about where vibe coding does not work — make it more specific.”
- “I want people to see the process, not just the result.”
All of this feedback is in Korean. Claude understands it perfectly and applies it to the English draft. This is the key insight: I am editing in my native language while the output is in a different language. I never have to struggle with finding the right English word or worrying about grammar. I just say what I mean in Korean and let Claude handle the translation layer.
Step 4: Claude revises and publishes.
After one or two rounds of feedback, the draft is ready. I say “publish it” and Claude connects to the server via SSH, creates the post in WordPress with all the formatting, and either publishes it immediately or sets it to a scheduled time. I never open the WordPress editor. I never copy-paste anything.
This Is Not Translation
I want to be clear about something: what Claude does is not translation. I am not writing a Korean article and asking it to convert it to English. I am giving directions in Korean and Claude is writing original English content based on those directions.
The difference matters. A translated article reads like a translated article — the sentence structure, the idioms, the flow all feel slightly off. What Claude produces reads like it was originally written in English, because it was. My Korean input is the creative direction, not the source text.
Think of it like this: a film director does not need to operate the camera to make a great movie. They need a vision, the ability to communicate that vision, and a skilled crew to execute it. I am the director. Claude is the entire crew.
What I Can Do That Google Translate Cannot
The feedback loop is what makes this work. Here are some real examples:
When Claude wrote the first version of my blog setup post, it was technically accurate but read like a tutorial. I told Claude in Korean: “This is too dry. I want it to feel like I am telling a friend about my weekend project, not writing documentation.” Claude rewrote the entire thing with a different tone. A translation tool cannot do that.
When I wanted to add a section about transparency — that AI wrote the post — I explained the concept in Korean and Claude understood not just what I wanted to say, but why I wanted to say it and how it should fit into the article’s narrative arc. A translation tool definitely cannot do that.
When I said “I want the process of making the post to be visible in the post itself,” Claude restructured the entire article around the conversation flow. It understood the meta-level intent: that the medium is the message. No translation tool on earth can handle that kind of nuance.
The Numbers
Let me give you some rough numbers for how long each post takes:
| Step | Time |
|---|---|
| Thinking about what to write | 5-10 min |
| Explaining it to Claude in Korean | 2-3 min |
| Claude writing the first draft | ~30 sec |
| Reading the draft and giving feedback | 5-10 min |
| Claude revising | ~30 sec |
| Final review and “publish it” | 2-3 min |
| Total | 15-25 min |
If I were writing these posts in English myself, each one would take at least 2-3 hours. And the result would be worse — more grammatical errors, less natural flow, more awkward phrasing. The AI is genuinely better at English writing than I am, and I am okay with that.
The Language Barrier Is Gone
This is the part that still feels kind of unreal to me. For my entire career, the English internet has been the bigger market — more readers, more ad revenue, more opportunities. But the language barrier always held me back. Not because I cannot communicate in English, but because I cannot write well in English. There is a huge difference between being able to order coffee in English and being able to write a blog post that people actually want to read.
AI erased that barrier. Completely. I can now publish English content that reads naturally, has the right tone, and conveys exactly what I want to say — all while thinking and directing entirely in Korean.
If you are a non-native English speaker who has been putting off creating English content, this workflow might change things for you too. You do not need to be fluent in English anymore. You just need to be fluent in your ideas.
How This Post Was Made
This one is extra meta. I told Claude in Korean: “Write a post about how I use you to write blog posts in English.” Claude pointed out the recursion and wrote it anyway. I gave feedback to add more specific examples from our actual conversations and to include the time breakdown table. Claude revised and published.
Total time from “let us write the next post” to published: about 20 minutes. Most of that was me reading and thinking about feedback, not typing.
This post was written with Claude AI. I provided the direction, topic, and key points in Korean — Claude turned it into the article you just read.