Most developers think we can't measure the performance of a software team.
But they're wrong.
In the book Accelerate, the authors define 4 indicators that determine if a team is performant or not. Efficiency being correlated to the level of quality of software practices.
🧵⤵️
The most important topic about software architecture is decoupling.
Clean, onion, and hexagonal architectures share this same principle: decouple the technical part of the code from its business side.
Here is why it's so crucial. A thread 🧵
Hexagonal Architecture 101: how do backend software engineers can easily decouple their code?
Also called "ports & adapters", this architecture is a simple method to ensure your project's evolutivity and maintainability.
A thread 🧵⤵️
How to onboard a new developer, so he loves working in your team?
Over the last few years, I've been working with several different teams. I've lived the dos and don't of onboarding.
A thread 🧵👇
Strategic Domain-Driven Design 101: how to align organizational and technical boundaries?
DDD is an approach to the development of complex software. Its goal is to reduce the gap between the business and the code. A thread 🧵⤵️
Strategic Domain-Driven Design 101 — 8 ways how 2 different software development teams can collaborate
To reorganize a 700k LoC app, I've been studying a lot of DDD's context mapping. It describes how teams can collaborate and which power dynamics exist between them
A thread 🧵
The 5 books I have learned the most from in my career 👇
I'd recommend those books to almost any developer, whatever their seniority level. I'll explain in which situation they can be useful and what you'll get out of them.
I wish I had it 5/6 years ago before moving to be part of a product team, there are so many real challenges and recommendations there that it was almost nostalgic some parts of the course, it would save me a lot of headaches.
Now it's time to go deeper into their references 🚀