What I’d Stop Doing in 2026 (As a Tech Lead)
The habits I’d leave behind in 2025
2025 didn’t teach me new frameworks. It taught me what to stop doing.
Stop pretending “everything can be solved in meetings.”
I’ve sat through 90-minute meetings that solved nothing. The team left drained, the code untouched.
In 2026, I’d prefer 15-minute laser-focused discussions that actually unblock work.
Stop ignoring the pain in tests.
Messy tests = slow dev, frustrated team. If it hurts, fix it—don’t ignore it.
I learned the hard way: a green test doesn’t mean safe. In 2026, I’d focus on fast, reliable TDD and readable acceptance tests—tests that guide, not confuse.
Stop letting legacy code scare you.
I used to avoid touching old modules. Change one thing, break ten others.
Now I tackle it in small, meaningful slices—refactoring as I go, using Hexagonal Architecture & Unit Tests, instead of hoping it “just works.”
Stop relying on one person to know everything.
Knowledge silos hide problems until it’s too late. When one engineer leaves, chaos follows.
In 2026, I’d share, document, and teach constantly, making the team resilient.
Stop chasing the “latest shiny framework.”
New frameworks are exciting—until they slow down the team.
Focus on fundamentals that actually make development faster and safer. Tools help, but clarity, reliability, and good architecture win every time.
The Real Shift
It’s not about new tech. It’s about removing friction from:
Tests
Dependencies
Everyday changes
Once that friction is gone, everything speeds up—without rushing. That’s where good architecture, TDD, and clear Hexagonal/clean code practices finally start paying off.
How can I help you in 2026?
Starting with TDD or Hexagonal Architecture can feel messy and risky if you don’t have a clear system-level safety net. That’s why we start with Acceptance Tests—covering behavior from the system level first.
🚀 Join me for Acceptance Testing (Live Training) on Wed 25th Feb (17:00 - 19:00 CET).
P.S. Regular price: $97 (free access for Optivem Journal paid subscribers - see event description for details)