"Taste" in software engineering
Maybe taste begins in not rushing to move on after AI has done its part.
We’re living in a time where creating something has never been easier.
An idea can turn into a prototype in a few hours. An app can be built in a day. An interface can be generated from just a few prompts.
Things that used to take a lot of time now have almost no friction.
And because of that, the way we work is starting to change.
There’s a style people call “vibe coding.”
Move fast. Try a lot. Don’t overthink.
I do that too.
But not to move forward faster.
I usually pause afterward.
When everything is already “working.”
Not to add more, but to see what can be taken away.
A slightly misaligned spacing.
A transition that feels a bit too fast.
A detail that isn’t wrong, but makes the whole experience feel a little heavier.
These are easy to overlook, especially when you can just move on to building the next thing.
Maybe the difference isn’t in how you use AI.
But in what you do after AI has done its part.
I’m not sure if that’s what “taste” is.
But maybe that’s where it begins.
In not rushing to move on.