49 karma · joined October 4, 2025
I write about engineering leadership, system design, and the uncomfortable truths behind tech’s productivity myths. Background in Node.js, React, TypeScript, and AI-driven architectures.
From Ukraine, currently working remotely with US-based companies. Obsessed with data, performance, and reducing noise in engineering management.
Interests:
Systems that improve engineering velocity without adding bureaucracy
AI in production (not demos)
Hiring accuracy, 90-day trials, and retention frameworks
The intersection of engineering culture, quality, and economics
The difference isn’t complexity it’s priorities. Jobs-era Apple had smaller teams building fewer products with obsessive quality standards. Cook-era Apple has massive teams shipping constantly with “good enough” as the bar.
You’re right that testing helps. But when quality becomes optional, no amount of testing infrastructure fixes the cultural problem. We test for “does it work?” not “is it excellent?”
These issues passed all automated tests. They just didn’t pass the “would we be embarrassed to ship this?” test. That test doesn’t exist anymore at scale.