I Learned That Building Is Mostly Making Decisions
When I started building online tools, I thought the hard part was coding.
Write the code.
Fix the bugs.
Publish the tool.
Done.
I was wrong.
The longer I build, the more I realize that coding is only one part of the work.
The harder part is deciding what should be built in the first place.
There Are Always Too Many Choices
Should this button be here?
Should I add another option?
Should the page have more information?
Should I change the layout?
Should I build a new feature or improve the existing one?
There is rarely one obvious answer.
And every decision takes time.
I Used to Avoid Decisions
Sometimes I kept adding things because making a decision felt uncomfortable.
“If I give users more options, they can choose.”
Sounds reasonable.
But more choices can also create more confusion.
I slowly learned that not deciding is also a decision.
And usually, it isn’t a very good one.
Simple Choices Are Not Always Simple
A clean page can take more thinking than a complicated one.
If I want a user to complete a task quickly, I have to decide what they actually need.
What can be removed?
What should be visible?
What can wait?
Get Bhavin Sheth’s stories in your inbox
Join Medium for free to get updates from this writer.
Those decisions often take longer than writing the code.
I Started Asking Better Questions
Instead of asking:
“What can I add?”
I started asking:
“What does the user need right now?”
That question makes things much clearer.
Sometimes the answer is a new feature.
Sometimes it’s better wording.
Sometimes it’s removing something completely.
Every Choice Has a Cost
A new feature isn’t just a few lines of code.
It may need testing.
It may create another setting.
It may need future updates.
It may make the interface harder to understand.
That’s why I now think about the cost of a feature before building it.
Not only the development cost.
The attention cost too.
Building Has Taught Me to Say No
This is probably one of the hardest lessons.
Not every good idea belongs in the product.
Not every request needs to become a feature.
Not every problem needs a complicated solution.
Sometimes saying no is how you protect the product.
What I Believe Now
Good building isn’t about making the most things.
It’s about making the right things.
Every product is a collection of decisions.
Some are visible.
Most aren’t.
But together, they determine how the product feels.
Final Thought
I started building because I enjoyed creating things.
Now I understand that the real work is often deciding what not to create.
The code comes after the decision.
The decision comes first.
