Jinho Kim

Essay · · 2 min read

Describe, don’t type

I can’t write code. I ship software anyway. Here is what the work turned into.

The road is there before you can see where it goes. Placeholder photo.

I started building software two years ago without knowing how to write any. I still can’t write much. What I do instead is describe: what the screen should do, what should happen when it fails, what I would be embarrassed to ship. A group of AI agents does the typing.

People hear this and imagine a shortcut. The work didn’t get shorter. It moved, and most of it moved to a place I wasn’t looking.

The description is the product

The first thing I learned is that a vague sentence produces vague software, and produces it instantly. “Add a settings page” returns a settings page: grey, complete, and chosen by nobody. Every decision I skipped still got made. I just wasn’t in the room.

So the descriptions changed. They didn’t get longer so much as sharper. Who is on this screen, and what are they trying to finish? What should they see first? What happens on the worst network, with the longest name, with nothing to show yet?

Structure you only notice from inside it. Placeholder photo.

Reading is not optional

The second thing took longer. For a year I treated the code as a sealed box: if the screen worked, the box was fine. Then a change passed every check I had, because no checks were running.1I wrote a short note about that week: Zero checks is not passing checks. Nothing failed. Nothing had been asked.

Now I read. Slowly, with a lot of questions, and not everything. But enough to know where things live and why they live there. You can’t judge a description of something you have never looked at.

What’s left for a person

Taste, mostly, and the nerve to stop.2Rams’s last principle is “as little design as possible.” Most days I settle for less than I started with, which is the point. To say this is finished, or this is wrong, or this looks like nobody chose it. An agent will happily keep going. Someone has to own the word no.

I don’t think any of this makes me an engineer. It makes me something closer to an editor with a very fast staff. The job is to know what good looks like, say it plainly, and check that it happened.

I’m still learning all three.