Stop punching yourself in the face!
summary
Software teams pick shiny tools and then pay for them: storing raw files in RavenDB cost vs S3; adopting an abandoned library like Agatha (no maintainer) vs Mediator; adding EventStore without training so one person becomes a bottleneck; misusing Entity Framework (first DbContext hit, N+1 queries, missing indexes, selecting wide rows); over-engineering with microservices for a simple CRUD app; and keeping legacy code alongside new frameworks instead of hollowing out the tree trunk — choose technical fit, check maintenance risk, train the team, and budget migration.
AI-written summary · about
chapters (4)
related talks
35mStop Punching Yourself in the Face
50mStop Punching Yourself in the Face
52mYour Brain on Software Development
53mMirror, mirror on the wall... Am I a critical thinker after all?
59mThe Tech Lead Elevator: Real Stories and Hard Lessons
45mFallacies of Software Development
48mThe Effective Software Architect - Work Smarter, not Harder
38mFallacies of Software Development
