How we built our equal-pay system
In this technical retrospective (2020), @hiatuscc 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 8 points
TOTAL DISCUSSIONS 2 comments
This seems like a good way to lose exceptional talent and be stuck with a bunch of mediocre or bad employees who will stick around as an easy way to get a raise.
Any self-respecting high-output employee is going to be offended at the fact that they're paid the same as someone who delivers 1/10 of the work. And yes, money is not the only factor in whether an employer is a good one. But for many it is the biggest factor.
This system is another push towards the ignorant idea that all people are the same. We're not all the same. Some people invest more in their careers. Those people will bring greater value to their employers, and they should be compensated in line with their abilities.
Good luck, though. Let us know in five years if all the virtue signaling actually pays off.
I skimmed over the article.
I assumed a lot of it is stock-based?