Articles

Blog

Des analyses approfondies sur l'architecture logicielle et la façon de structurer le code source — écrites pour être comprises par les débutants, tout en restant utiles aux équipes qui livrent à grande échelle. Des schémas, des exemples concrets, sans bla-bla.

Parcourir par thème

Code source & Architecture

Comment organiser le code source pour qu'il survive à la croissance, aux équipes et aux changements.

11 articles

Culture d'ingénierie

Le côté humain de la construction de logiciels — revues, retours, mentorat, et les équipes qui font grandir les personnes plutôt que de les épuiser.

6 articles

IA & L'Avenir

Comprendre l'IA — de l'ingénierie de contexte à la construction de produits IA fiables.

9 articles

Perspectives & Field Notes

Personal reflections from work, learning, people, and the quiet moments that shape a career.

1 article

Ways of Working

How software teams actually operate and work together — from Agile and Scrum to how delivery really happens in big corps, startups, and outsourcing.

20 articles

Derniers articles

Tags populaires

47 articles

IA & L'Avenir

Cognitive Debt in AI-Assisted Development: When Code Grows Faster Than Understanding

AI coding tools can make a team produce code faster than it can understand, review, debug, and safely operate that code. This article explains cognitive debt, how it differs from technical debt and intent debt, why agentic coding makes it more visible, and the practical controls teams can use: smaller batches, better PR rationale, human-owned invariants, disposable prototypes, and AI used to repay understanding instead of only generating more work.

17 juin 202615 min de lecture

Ways of Working

Lean Business Analysis: Start from Value, Not Requirements

A practical introduction to Lean Business Analysis: why BA starts with value, how needs assessment protects teams from solving the wrong problem, and how a business case keeps decisions grounded without turning analysis into ceremony.

17 juin 202613 min de lecture

Ways of Working

Lean BA Planning: Stakeholders, Elicitation, and the Questions Behind Requirements

A practical guide to Lean BA planning: stakeholder analysis, predictive versus adaptive BA rhythms, elicitation planning, and the difference between collecting stated requests and uncovering the need behind them.

17 juin 202614 min de lecture

Ways of Working

Requirements Modeling: How BA Turns Messy Conversations into Shared Pictures

A calm, practical guide to requirements modeling: scope, process, rule, data, and interface models, with examples of how diagrams and structured descriptions help teams reason together before building.

17 juin 202615 min de lecture

Ways of Working

Requirements Quality, Traceability, and Solution Evaluation: Keep the Promise After Sign-off

A practical reflection on the later half of Business Analysis: requirement quality, prioritization, traceability, change control, UAT, rollout choices, transition, and evaluating whether the delivered solution actually worked.

17 juin 202615 min de lecture

Ways of Working

Software Measurement and Estimation: Fewer Gut Feelings, Better Engineering Decisions

A practical reflection on Software Measurement and Estimation: A Practical Approach by Linda M. Laird and M. Carol Brennan. The article focuses on the ideas engineers can use at work: measure from decisions, estimate as uncertainty instead of promise, track quality before release, and keep dashboards useful instead of decorative.

17 juin 202616 min de lecture

Ways of Working

Agile Estimating and Planning: Estimates Are Conversations, Not Promises

A practical reflection from Mike Cohn’s Agile Estimating and Planning on story points, velocity, planning poker, ideal days, and why estimates should expose uncertainty instead of pretending to remove it.

17 juin 202613 min de lecture

Ways of Working

Agile Release Planning: Plan with Value, Risk, and Real Feedback

A second reflection from Agile Estimating and Planning, focused on release planning: prioritizing by value and risk, splitting stories into useful slices, using buffers for uncertainty, and communicating plans without pretending the future is fixed.

17 juin 202618 min de lecture

Ways of Working

The Design of Everyday Things: Make the Interface Explain Itself

A practical reflection from Don Norman’s The Design of Everyday Things for software and product teams: discoverability, signifiers, mapping, feedback, conceptual models, and why a clear interface should not make users guess what it wants.

17 juin 202612 min de lecture