Product thinking
Building software that solves a real problem
I’ve noticed that my better project ideas usually don’t begin with a technology. They begin with something annoying.
Someone is standing in a grocery aisle trying to remember what an item cost somewhere else. Posting a food photo takes more steps than taking the photo itself. A small business owner needs to change a price without calling the person who built the website.
Those situations give me something concrete to work from. Before I worry about the framework or database, I can ask what the person is trying to do, what is getting in the way, and what I can remove.
I still care about the code underneath it. I just don’t want the code to become the reason the product exists.
That’s something I’m trying to get better at with every project: start with the real problem, build the smallest useful answer, put it in front of people, and learn from what happens next.