Database Design Decisions Nobody Talks About
When you're building a system from scratch,
every architectural decision feels important.
And honestly? Some of them really are. But after
working with dozens of companies across
Taichung's manufacturing and logistics sectors,
we've noticed patterns.
The decisions that seem trivial at first—like
how you name your foreign keys or whether you
normalize that one table—end up mattering way
more than the big architectural debates everyone
focuses on.
We've learned this the hard way. By inheriting
systems where small decisions compounded into
maintenance nightmares. And by making some of
those mistakes ourselves early on.
Linnea Voss
Lead architect who's spent the last seven
years fixing other people's database
designs—and occasionally her own.