The thing vibecoding taught me about my own taste
I did not realize how much of my job was taste until I started generating code fast.
When you can produce ten versions of a feature in an afternoon, the bottleneck moves. It is no longer how fast you can build. It is how well you can tell which version is good. And that skill lives completely outside the tool.
I have generated plenty of things that technically worked and were the wrong choice. Too much surface. Wrong emphasis. The kind of thing that passes a test and fails a person. The model will happily build whatever I describe, including my bad ideas, with the same confidence it gives my good ones.
So the more I vibecode, the more I care about judgment. What to build, what to cut, what to leave ugly on purpose.
That part is still entirely mine and I am not sure it can be outsourced.
Do you feel the same? Has speed made the taste part more or less important for you?
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.