Engineering August 21, 2025 5 min read
What I Learned Building Software Inside a Real Business
Working in a refrigeration business taught me more about good software than any framework ever did.
Most developers learn software from the outside in: frameworks first, problems later. I got lucky and learned it the other way around.
The problem came before the code
Before I was writing ERP modules, I was watching people struggle with stock counts, double-entered bills, and month-end chaos in a refrigeration business. The software wasn't an abstract exercise — it was a fix for a headache I could see on people's faces.
Lessons that stuck
- The feature list is never the real requirement. People ask for a button; what they need is to stop making a mistake. Build for the mistake.
- Adoption beats elegance. A clever system nobody uses is worth nothing. The boring, obvious flow that staff actually follow wins every time.
- Numbers are the product. If the software doesn't make a metric move — time saved, errors cut, sales found — it's decoration.
That perspective is the thing I bring to every project now: I'm not just shipping code, I'm shipping a result the business can measure.
#Career#ERP#Product