Turning Review Evidence Into Team Memory
A practical note on converting review findings, commands, screenshots, and decisions into reusable team memory instead of one-time approval artifacts.
Articles
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.
Comment organiser le code source pour qu'il survive à la croissance, aux équipes et aux changements.
41 articlesLe 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.
41 articlesComprendre l'IA — de l'ingénierie de contexte à la construction de produits IA fiables.
41 articlesPersonal reflections from work, learning, people, and the quiet moments that shape a career.
31 articlesHow software teams actually operate and work together — from Agile and Scrum to how delivery really happens in big corps, startups, and outsourcing.
50 articlesA practical note on converting review findings, commands, screenshots, and decisions into reusable team memory instead of one-time approval artifacts.
A reflective note on how a month of small daily observations can reveal patterns that are easy to miss in the middle of work.
A practical reflection on using AI to broaden investigation while keeping source checking, trade-off decisions, and accountability with people.
A calm note on treating attention as a shared team resource, not an infinite personal budget that people can recover alone.
A practical reflection on choosing defaults that protect users and systems when configuration, rollout, or external dependency behavior is uncertain.
A practical note on writing handoffs that include open questions, assumptions, and risk instead of pretending the work is more certain than it is.
A reflective note on the small discipline of closing work with evidence, cleanup, and context instead of only reaching the visible finish line.
A practical reflection on making AI-assisted work safer by asking the model to expose assumptions before accepting its answer.
A calm note on treating repeated team friction as useful signal before it hardens into personal blame.