Using Zig to provide stack traces on kernel panic on bare metal (2018)
In this technical retrospective (2020), @brianush1 shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Pandemic Bubble (2020–2022)
COMMUNITY SCORE 141 points
TOTAL DISCUSSIONS 10 comments
Ok, is it just me or is Andrew Kelley a one-person, prodigy coding machine? I’ve been following Zig’s development for a few years now and the technical wizardry he’s gone through to develop a powerful, innovative language that is self hosted, challenges all the new systems languages out there, compiles C and supports magical cross compilation is just mind blowing to me.
Thanks Andrew for pushing the boundaries and rethinking what can be possible with modern tooling.
I highly recommend people to watch his live streams. Excellent stuff.
I once helped an engineer to bring up a custom board running an AMD 286 ... it had a strip of LED's which our boot loader would trigger at various points while it initialized the various bits.
No LED meant it was time to bring out the oscilloscope.
Needs [2018]
Previous discussion: https://news.ycombinator.com/item?id=18603632 ↗