The Obsession with Customer Service
When “users” are mistreated by a company in a monopoly position, there is cause to start a competing business.
Blog
Enabling Change: A Different Type of Assignment for Every Situation
Even though every project is unique, it’s still possible to identify common types, starting with the “firefighter” project: “Help, everything’s on fire!”
12 Creative Ways to Screw Up Your Sprints
"It’s good to learn from your mistakes. It’s better to learn from the mistakes of others." Warren Buffett is talking about investing; I’m talking about sprints.
Why I Write
I’ve been writing every week for over two years now. This is an opportunity to reflect on what truly motivates me, beyond the simple pleasure of sharing my experience.
Command-Query Responsibility Segregation
CQRS is based on the idea of distinguishing between write and read models when operations are highly asymmetric. Use sparingly.
100% Code Coverage: The Never-Ending Race
This metric isn’t very useful if you don’t know what it represents… However, it’s still interpretable—especially when it’s low!
Waterfall: A Recipe for Failure
Sequential methodologies do not work for business IT, primarily because of the tunnel effect. The alternative? Agility.
50 shades of tests
Not all tests fit into a single test pyramid. Several aspects must be considered: purpose, granularity, and assertion methods.
The Very Best Of
To mark the 100th issue of this newsletter, here’s a selection of 10 articles—some of your favorites and some of my personal favorites.
An architecture that leaves doors open
"The job of an architect is to build a structure that allows decisions to be delayed as long as possible": 5 examples illustrating Uncle Bob’s point.
End-to-end tests: how to get off on the right foot
End-to-end tests should be used sparingly, as they are costly to write (Page Model) and costly to run. Here’s how to proceed.
My Values
Joy, humility, rigor, and action. These are the values that drive me, both in my daily life and at work—the two cannot be separated.
The Retrospective: The DNA of Agility
If you had to keep just one thing from Agility, keep the retrospective. As a forum for continuous improvement, it paves the way for problem-solving.
An X student who writes code
For me, being a Polytech graduate meant an obligation to hold high-level positions, and part of me aspired to that out of a need for recognition.
Product: when you get attached to your baby")
We take care of a product, we help it grow, we tend to it day after day just as we care for a baby. We become attached to it, and that’s perfectly fine.
Markup, rip-off: what if we rethought how intermediaries are compensated?
The intermediary brings their full value to the signing of the contract, not to every day of the assignment. Their compensation should therefore be a flat fee.
Software quality—is it all about the code?
Software quality isn’t just about code: it’s a matter of product, agility, organization, and people, before it is a matter of technical expertise.
Coach or consultant?
While a consultant provides specific answers, a coach helps their client find their own answers. These are different yet complementary approaches.
Architecture Decision Record
ADR helps streamline a team’s architectural decisions and prevents them from being constantly called into question.
"If you want to [program] better, stop [programming] for two years"
In our eagerness to master our craft, we sometimes come to view computer science as an end in itself. Yet it is merely a means. A means to what end?