5 Lessons from Building Software for a Furniture Factory (That Apply Everywhere)

Jane — Wed, 22 Oct 2025 13:05:35 +0000

I'm Jane, and I write code that helps turn wood into wardrobes at Juventa Furniture. Working on the factory floor has taught me more about software development than any bootcamp could. Here are five lessons that apply way beyond manufacturing.

1. Users Don't Read Documentation (Especially When Wearing Gloves)

Our factory workers interact with touchscreens while wearing protective gloves, often with sawdust in the air. If they need to read a manual, I've failed.

The lesson: Design for the worst-case scenario. If your interface needs explanation, it needs redesign. This applies to every user-facing app, not just industrial ones.

2. Downtime Costs Real Money (Like, A Lot)

When our manufacturing execution system goes down, the entire production line stops. That's $500+ per minute in lost productivity. No pressure.

The lesson: Reliability isn't a nice-to-have; it's everything. Build in redundancy, plan for failure modes, and always have a rollback strategy. Your SaaS uptime matters more than you think.

3. "Good Enough" Data Beats "Perfect" Data That Doesn't Exist

I wanted precision inventory tracking down to the millimeter. Workers wanted to scan a barcode and move on. We compromised with ±5cm accuracy that updates in real-time.

The lesson: Don't let perfect be the enemy of done. A working 80% solution today beats a theoretical 100% solution next quarter. Ship it, then iterate.

4. The Best Code is Code That Runs Offline

Internet goes down? Factory keeps running. Our edge devices cache everything locally and sync when connectivity returns.

The lesson: Never trust the network. Build offline-first, sync-when-possible. Whether it's a factory or a mobile app, assume connectivity is a bonus, not a guarantee.

5. Talk to Your Users (Even If They Speak a Different Language)

My first dashboard was full of technical metrics. Workers wanted to know: "Are we on track for today's quota?" That's it.

The lesson: Your users' mental model isn't your mental model. Spend time understanding what they actually need, not what you think they need. The best feature is often the simplest one.

Bonus: Physical Constraints Make You a Better Developer

When your bug can jam a saw blade or waste €500 worth of oak, you learn to test thoroughly. When your UI needs to work on a decade-old industrial PC, you learn to optimize. When workers rely on your system for their daily workflow, you learn to care about UX.

Manufacturing software isn't glamorous, but it's made me a better developer. Every line of code has immediate, visible consequences. That clarity is a gift.