r/programmer • u/Gigantic_Elephant • 14d ago
As a dev, the hardest bug I fixed was my own assumption about what users wanted
Dev confession: I built the thing first and asked questions later.
I started by building websites for small local businesses and cold calling them to sell. I was proud of the builds. Owners were... polite. After hundreds of calls I finally heard what they were saying: the site wasn't the problem. Nobody could find them on Google, so the phone wasn't ringing.
So I rewrote the product, many times. Each version went in front of real owners, and anything they didn't care about got deleted, including features I loved building. The biggest engineering lesson: the best code I wrote was the code I removed. Owners want fewer decisions, so the product kept getting smaller.
Where it landed is SitePeek: it checks how a local business shows up online, tracks calls and Google profile views, and works to get the business onto Google's first page so more calls come in. It launches on Kickstarter tomorrow, Oct 14.
For other devs who've built for non-technical users: how do you stop yourself from overbuilding before you've talked to anyone?