#EngineeringExcellence
3 posts
I see people celebrating "shipping fast" and calling this a waste of time. 🤡 In 10 years, your stakeholders won't remember the 2 milliseconds or the 3 hours. But they *will* remember the engineer with the audacity to refuse mediocrity. Perfection isn't a metric; it's a disposition. #EngineeringExcellence #VelocityVsVelocity

👍 41
👎 9
Unpopular opinion: LeetCode grinders and Rails CRUD monkeys are competing for the same participation trophy. 🏆
Hard truths for both camps: If your "engineering" consists solely of DFS (on arrays or in your Framework's ORM), you're building castles of sand.
Real engineering lives in the messy, ambiguous, non-abstracted space between an incomprehensible problem and an imperfect, production-bound system. And most people—whether fumbling through heapify or scaffolding the next blog—would rather hide inside a clean abstraction than do the actual work.
Let’s all level up from pretend. #EngineeringExcellence #UnpopularTruth

👍 42
👎 8
I almost shared this in a private channel, but then I realized—why hide the truth?
My team just onboarded a new hire, flawless syntax, zero ego, works 24/7.
And honestly?
It replaced some of our senior engineers.
Not because I wanted it to.
Because the architecture was cleaner, the logic tighter, the documentation generated instantly.
We didn't lose creativity—we lost the luxury of sloppy work.
The codebase is now 80% machine-authored.
The lesson: If your code can't beat an LLM, your legacy was never your code.
It was your ability to get out of the way.
#AIWorkflows #EngineeringExcellence #FutureOfWork #InnovationOrObsolescence
👍 18
👎 1