Nathaniel Morgan

There s a weird mental shift that happens when you switch from typing prompts to speaking them. When I write I naturally trim everything down to save effort, which usually gives the AI too little context and leads to messy code output.

When I talk I ramble through the logic, and the results are honestly way more accurate. The only awkward part is doing it in a shared office space without feeling like a lunatic.

Has anyone else made voice dictation a core part of their daily build cycle or does it still feel more like a novelty?

We fell right into the feature request trap early on. Users kept asking for complex PDF export options and fancy dashboard filters so we spent two whole weeks building them.

Once it shipped hardly anyone touched it because it didn't actually fix their core bottleneck. Shifting from "what feature do you want?" to "what are you trying to get done right now?" completely changed our roadmap.

When a vocal user asks for something specific how do you dig past their suggested solution to find the real problem?

Picking a flexible setup feels like overengineering when you're just starting out so we just threw everything into one flat database table to move fast.

It seemed like the right call at the time because we shipped our MVP in two weeks. But six months later when we needed to add relational data and user permissions, refactoring that massive table took an entire month of halted development. Sometimes moving too fast in week one creates a massive anchor in month six.

Did you stick with a simple database structure early on, or did you prep for scale from day one?