SOLID Software Developer
@qpautrat.bsky.social
Objectivement objectif - Head of Engineering @wakam
#DDD #DesignPatterns #BDD #TDD #Agile #SoftwareTeaming
qpautrat.fr
#DDD #DesignPatterns #BDD #TDD #Agile #SoftwareTeaming
qpautrat.fr
Reposted by SOLID Software Developer
Even if the fantasy that AI will speed coding by 100% or more were true, it would not decrease lead time. Firing half of your people because of an immagined 100% improvement in the other half will also not relieve the bottleneck.
9/10
9/10
December 21, 2025 at 6:29 PM
Even if the fantasy that AI will speed coding by 100% or more were true, it would not decrease lead time. Firing half of your people because of an immagined 100% improvement in the other half will also not relieve the bottleneck.
9/10
9/10
Reposted by SOLID Software Developer
Work is always relative to what others are doing, using available tools. To be best-in-the industry, you need to have either higher quality output than everyone else, or more output than everyone else.
So if everyone uses better tools: you'd either do better work with them, or work more!
So if everyone uses better tools: you'd either do better work with them, or work more!
December 23, 2025 at 8:28 AM
Work is always relative to what others are doing, using available tools. To be best-in-the industry, you need to have either higher quality output than everyone else, or more output than everyone else.
So if everyone uses better tools: you'd either do better work with them, or work more!
So if everyone uses better tools: you'd either do better work with them, or work more!
Reposted by SOLID Software Developer
What IS a mistake (in my opinion) is to apply this tried-and-tested approach to software design (i.e., divide-and-conquer, separation-of-concerns, etc.) to the software development/delivery process. Creating silos in the flow (i.e., the value delivery stream) is a terrible idea.
December 9, 2025 at 10:48 PM
What IS a mistake (in my opinion) is to apply this tried-and-tested approach to software design (i.e., divide-and-conquer, separation-of-concerns, etc.) to the software development/delivery process. Creating silos in the flow (i.e., the value delivery stream) is a terrible idea.
Reposted by SOLID Software Developer
In terms of resiliency, it doesn't matter that the internet is distributed if there's monopoly on top of that.
December 5, 2025 at 11:01 AM
In terms of resiliency, it doesn't matter that the internet is distributed if there's monopoly on top of that.
Reposted by SOLID Software Developer
Prior to 2025: “Code should be self documenting”
2025: “Documents should be self coding”
2025: “Documents should be self coding”
November 7, 2025 at 3:33 AM
Prior to 2025: “Code should be self documenting”
2025: “Documents should be self coding”
2025: “Documents should be self coding”
Reposted by SOLID Software Developer
The fact that some problem is complicated often stems from its not being sufficiently broken down. An "if" statement in a user story, for example, tells me that it's actually two stories, one for the "if" branch and one for the "else." Complex problems are often packed with logic of that sort.
2/7
2/7
November 2, 2025 at 4:58 PM
The fact that some problem is complicated often stems from its not being sufficiently broken down. An "if" statement in a user story, for example, tells me that it's actually two stories, one for the "if" branch and one for the "else." Complex problems are often packed with logic of that sort.
2/7
2/7
Reposted by SOLID Software Developer
For example, organizations that use mob/ensemble programming 100% of the time do not need standups. (And, just to cut off the comment: no, that is not less efficient. Many ensembles work faster than they did when they were working as individuals.)
6/10
6/10
October 13, 2025 at 3:25 PM
For example, organizations that use mob/ensemble programming 100% of the time do not need standups. (And, just to cut off the comment: no, that is not less efficient. Many ensembles work faster than they did when they were working as individuals.)
6/10
6/10
Reposted by SOLID Software Developer
You cannot make even small changes to a system of work without considering the system as a whole and making systemic adjustments.
So, if you want to remove that standup, you need to adjust the overall system to compensate.
5/10
So, if you want to remove that standup, you need to adjust the overall system to compensate.
5/10
October 13, 2025 at 3:25 PM
You cannot make even small changes to a system of work without considering the system as a whole and making systemic adjustments.
So, if you want to remove that standup, you need to adjust the overall system to compensate.
5/10
So, if you want to remove that standup, you need to adjust the overall system to compensate.
5/10
Hofstadter’s Law
Estimating big things is hard
- Slice until lead time matches your feedback horizon
- The best way to estimate is to see how long similar work took!
- Plan by capacity and flow limits rather than wishful point totals.
fffej.substack.com/p/social-and...
Estimating big things is hard
- Slice until lead time matches your feedback horizon
- The best way to estimate is to see how long similar work took!
- Plan by capacity and flow limits rather than wishful point totals.
fffej.substack.com/p/social-and...
Social and Organizational Heuristics
Mental Models that might be useful.
fffej.substack.com
September 16, 2025 at 2:42 PM
Hofstadter’s Law
Estimating big things is hard
- Slice until lead time matches your feedback horizon
- The best way to estimate is to see how long similar work took!
- Plan by capacity and flow limits rather than wishful point totals.
fffej.substack.com/p/social-and...
Estimating big things is hard
- Slice until lead time matches your feedback horizon
- The best way to estimate is to see how long similar work took!
- Plan by capacity and flow limits rather than wishful point totals.
fffej.substack.com/p/social-and...
Reposted by SOLID Software Developer
I have often been told when advocating for team autonomy that some teams want to be told what to do. They often feel uncomfortable when making decisions.
1/9
1/9
August 25, 2025 at 11:33 PM
I have often been told when advocating for team autonomy that some teams want to be told what to do. They often feel uncomfortable when making decisions.
1/9
1/9
1/
I relate to this 10000% !!
18 months ago we started using a LC/NC tool for all our internal domain-centric apps. True, deployment speed is unbeatable — the entire app IS in production before you even begin.
I relate to this 10000% !!
18 months ago we started using a LC/NC tool for all our internal domain-centric apps. True, deployment speed is unbeatable — the entire app IS in production before you even begin.
Low-Code/No-Code tools are everywhere in 2025. They promise speed and empower “citizen developers.”
But there’s the trade-off. Short-term wins vs. long-term complexity. Without engineering discipline, these systems often become the very bottlenecks they were meant to remove 🤷♂️
But there’s the trade-off. Short-term wins vs. long-term complexity. Without engineering discipline, these systems often become the very bottlenecks they were meant to remove 🤷♂️
August 25, 2025 at 10:10 PM
1/
I relate to this 10000% !!
18 months ago we started using a LC/NC tool for all our internal domain-centric apps. True, deployment speed is unbeatable — the entire app IS in production before you even begin.
I relate to this 10000% !!
18 months ago we started using a LC/NC tool for all our internal domain-centric apps. True, deployment speed is unbeatable — the entire app IS in production before you even begin.
I like this idea of "production-readiness". In my future job I could sell myself as a "production-readiness" expert for vibe coded app. I tell you it is not, why, and how I would fix it.
Wait... Seems familiar 🤔
But it could be a new Job title.
Wait... Seems familiar 🤔
But it could be a new Job title.
1. To build production-ready apps, you need expertise to verify for production readiness. This is far more than “just” a checklist (that most such platforms do)
2. LLMs cannot audit an app for production-readiness… it’s a hard task even for devs! Companies charge a lot for audits for good reason…
2. LLMs cannot audit an app for production-readiness… it’s a hard task even for devs! Companies charge a lot for audits for good reason…
August 6, 2025 at 2:42 PM
I like this idea of "production-readiness". In my future job I could sell myself as a "production-readiness" expert for vibe coded app. I tell you it is not, why, and how I would fix it.
Wait... Seems familiar 🤔
But it could be a new Job title.
Wait... Seems familiar 🤔
But it could be a new Job title.
Reposted by SOLID Software Developer
Tests tell us our software can work.
Observability tells us our software IS working.
Observability tells us our software IS working.
August 3, 2025 at 12:11 AM
Tests tell us our software can work.
Observability tells us our software IS working.
Observability tells us our software IS working.
Reposted by SOLID Software Developer
Funny how we force engineers to write ADRs for every trade‑off, yet billion‑dollar strategic bets live in hallway whispers and fluffy slide decks.
What if we treated business decisions like architecture? Context, options, trade‑offs, metrics, all in a repo, version‑controlled and reviewed?
What if we treated business decisions like architecture? Context, options, trade‑offs, metrics, all in a repo, version‑controlled and reviewed?
July 17, 2025 at 3:35 AM
Funny how we force engineers to write ADRs for every trade‑off, yet billion‑dollar strategic bets live in hallway whispers and fluffy slide decks.
What if we treated business decisions like architecture? Context, options, trade‑offs, metrics, all in a repo, version‑controlled and reviewed?
What if we treated business decisions like architecture? Context, options, trade‑offs, metrics, all in a repo, version‑controlled and reviewed?
Reposted by SOLID Software Developer
The irony is that dev teams who work in ways that appear to get the best results from LLMs - small steps, prompting with tests, rapid feedback loops, continuous testing, code review and integration, and good separation of concerns - have little need for the tools.
July 9, 2025 at 1:39 PM
The irony is that dev teams who work in ways that appear to get the best results from LLMs - small steps, prompting with tests, rapid feedback loops, continuous testing, code review and integration, and good separation of concerns - have little need for the tools.
Reposted by SOLID Software Developer
Hmmm. "A well-designed external feedback loop (linters, tests, mutation checks) beats a static claude.md file by far, probabilistically speaking."
Interesting. More grist for my "External Sources of Truth" principle.
Interesting. More grist for my "External Sources of Truth" principle.
July 5, 2025 at 5:46 AM
Hmmm. "A well-designed external feedback loop (linters, tests, mutation checks) beats a static claude.md file by far, probabilistically speaking."
Interesting. More grist for my "External Sources of Truth" principle.
Interesting. More grist for my "External Sources of Truth" principle.
So it appears we experiencing one of the biggest paradigme shift in the history of our profession. Let's assume it's the case (and I tend to think it is but does not mean it's absolute). Then it would be very surprising that...
martinfowler.com/articles/202...
martinfowler.com/articles/202...
LLMs bring new nature of abstraction
A long-form article entitled: "LLMs bring new nature of abstraction"
martinfowler.com
June 25, 2025 at 9:26 PM
So it appears we experiencing one of the biggest paradigme shift in the history of our profession. Let's assume it's the case (and I tend to think it is but does not mean it's absolute). Then it would be very surprising that...
martinfowler.com/articles/202...
martinfowler.com/articles/202...
Reposted by SOLID Software Developer
(comic) Temporary fix
June 25, 2025 at 4:28 PM
(comic) Temporary fix
Reposted by SOLID Software Developer
Vibe coding is the game of moving fast. Meaning, moving fast to the next org without having to stay and maintain the code produced by vibing.
June 17, 2025 at 1:59 AM
Vibe coding is the game of moving fast. Meaning, moving fast to the next org without having to stay and maintain the code produced by vibing.
Reposted by SOLID Software Developer
Just a regular reminder that predictability (and accuracy of estimates) goes down the drain as you overload the system with too much WIP?
How much WIP is too much WIP?
How much WIP is too much WIP?
June 17, 2025 at 6:57 AM
Just a regular reminder that predictability (and accuracy of estimates) goes down the drain as you overload the system with too much WIP?
How much WIP is too much WIP?
How much WIP is too much WIP?
Reposted by SOLID Software Developer
From an engineering perspective, software wants to be decoupled. From a business value perspective, software wants to be deeply interconnected. That's the fundamental friction that software design, and Domain-Driven Design specifically, attempts to address.
June 6, 2025 at 7:57 AM
From an engineering perspective, software wants to be decoupled. From a business value perspective, software wants to be deeply interconnected. That's the fundamental friction that software design, and Domain-Driven Design specifically, attempts to address.
Reposted by SOLID Software Developer
I could use a nice trip to somewhere in Europe or the UK.
I'd like to sponsor my trip by doing useful work with your company. I have a lot of skill and experience in software delivery, code craft, and team management.
Consider contracting me for a few days. I would love to help.
I'd like to sponsor my trip by doing useful work with your company. I have a lot of skill and experience in software delivery, code craft, and team management.
Consider contracting me for a few days. I would love to help.
May 22, 2025 at 10:49 AM
I could use a nice trip to somewhere in Europe or the UK.
I'd like to sponsor my trip by doing useful work with your company. I have a lot of skill and experience in software delivery, code craft, and team management.
Consider contracting me for a few days. I would love to help.
I'd like to sponsor my trip by doing useful work with your company. I have a lot of skill and experience in software delivery, code craft, and team management.
Consider contracting me for a few days. I would love to help.
Reposted by SOLID Software Developer
#important : suite à l’invitation de @TiboInShape pour interviewer le président de la république, nous demandons aux organisateurs de l’émission de nous rajouter dans le pool des intervenants et appelons notre communauté à relayer massivement cette demande journalistique, déontologique et légitime.
May 10, 2025 at 3:15 PM
#important : suite à l’invitation de @TiboInShape pour interviewer le président de la république, nous demandons aux organisateurs de l’émission de nous rajouter dans le pool des intervenants et appelons notre communauté à relayer massivement cette demande journalistique, déontologique et légitime.
Is GenAI really revolutionizing software development? 🧐
The answer is not necessarily obvious if we believe the latest study from DORA.
What is certain is that it deserves our attention.
With the teams, we dove into the deep end with a code kata 100% assisted by AI.
The answer is not necessarily obvious if we believe the latest study from DORA.
What is certain is that it deserves our attention.
With the teams, we dove into the deep end with a code kata 100% assisted by AI.
Kata de code assisté par IA: Une expérience d'équipe sur cette pratique émergente
Retour d'expérience d'un kata de développement assisté par l'IA, révélant des enseignements clés sur les gains de productivité, l'entropie logicielle et les stratégies pratiques d'implémentation pour ...
qpautrat.fr
April 30, 2025 at 8:42 AM
Is GenAI really revolutionizing software development? 🧐
The answer is not necessarily obvious if we believe the latest study from DORA.
What is certain is that it deserves our attention.
With the teams, we dove into the deep end with a code kata 100% assisted by AI.
The answer is not necessarily obvious if we believe the latest study from DORA.
What is certain is that it deserves our attention.
With the teams, we dove into the deep end with a code kata 100% assisted by AI.
Reposted by SOLID Software Developer
Mob/ensemble guarantees both:
— availability (by design, everyone needed is in the session), and
— resiliency of flow (if someone drops, the show can go on).
— availability (by design, everyone needed is in the session), and
— resiliency of flow (if someone drops, the show can go on).
April 21, 2025 at 9:33 AM
Mob/ensemble guarantees both:
— availability (by design, everyone needed is in the session), and
— resiliency of flow (if someone drops, the show can go on).
— availability (by design, everyone needed is in the session), and
— resiliency of flow (if someone drops, the show can go on).