What Working With a Greek Engineer Taught Me
Multiple rounds of code review, days-long debates, real disagreements — and the things that actually stuck after the project ended.
Multiple rounds of code review, days-long debates, real disagreements — and the things that actually stuck after the project ended.
A 9:1 read-write ratio is real, but it doesn't automatically mean your relational schema is wrong. A monolith on plain Postgres handles most traffic, most slow pages have cheaper fixes than re-architecting, and when a join genuinely is the bottleneck, a denormalized read table inside the same database solves it. No NoSQL or microservices required.
I've worked across Angular, Blazor, React, .NET, multiple architectures, and a dozen domains. Here's what that actually taught me — and why the label was the first thing to go.