Men, mission, me
A leader's priorities, in order: serve the team, deliver the mission through them, put yourself last. Invert any of the three and you stop leading.
Distilled thoughts from the tech industry and literature
A leader's priorities, in order: serve the team, deliver the mission through them, put yourself last. Invert any of the three and you stop leading.
Unanimous decisions can hide real objections. Psychological safety and structured dissent surface them before sunk costs harden a bad call.
The supply of senior engineers does not refill itself. Cutting juniors to fund AI tooling looks clean on a quarter but corrodes a five-year horizon.
Generative AI makes writing code faster. That speeds up a step that was rarely the constraint, while piling pressure on the ones that always were.
AI accelerates code creation, but engineering still depends on clarity and judgment. Without taste and good feedback loops, speed compounds the debt.
Effective systems are engineered through sound judgment and deliberate decisions. Fear undermines both at the root.
Architecture mirrors how your teams communicate, not how the wiki diagrams say it should. To change the system, change the org chart first.
A $2M failure no code review would catch. Organizational Behavior is the science of why most projects fail in the human system, not the technical one.
Mastering the skills to succeed in remote work without missing a beat in the office
Scaling the Heights of Impact: A guide for software engineers and the leads who inspire them
Unraveling the art of making complexity understandable
Some ideas for your first steps
How self-interest can undermine a group's outcome
'I would do it but I'm not feeling motivated right now'. How often do you feel like that?
Learn how to avoid double writes, a common pitfall of microservices design
A motivational discussion with wonderful career advice for technology professionals
spoiler: DevOps to the rescue
Making the «right» choice is not as important as you think
Slack time is vital to growth
The patterns and trade-offs in these books outlast every framework cycle.
What do we mean by resiliency, why is it so important for cloud systems, and what is it primarily based upon?
The Not Invented Here syndrome is a disease for the software industry. Learn how to spot it and prevent it.
3+1 root causes of high code churn that can kill your project
Is it all about fast results? What's your true role as an engineer?
Why are we so confused about this?
Another metaphor about professionalism in software development
A metaphor about professionalism in software development
Apply modern Building techniques to any version of ASP.NET
'Blending ASP.NET MVC with Angular' post series
Knowing when to act is equally important to knowing when not to
No matter what your reasons are for pursuing a master's degree, here's how to make the most out of it.
On November the 2nd, I had the honor of being a guest speaker at the National College of Ireland
Keeping classes small and focused is key for eliminating both technical debt and numerous code smells
I must admit that I used to be a bit territorial about my code, but not anymore, and let me tell you why.
Recommended reading on engineering leadership, software architecture, craft, and career.
Geoff provides an excellent starting point for creating sound and maintainable cloud architectures.
Rewiring the world from Edison to Google
Even the best idea can be doomed from day one if the entrepreneur is not familiar with a suitable process needed to turn that idea into a successful company.
Browse the archive → Older posts kept for historical reasons.