Lehmann Emmanuel

Albert Einstein a dit : « Tenez-vous loin des personnes négatives. Elles ont un problème pour chaque solution. »

The idea of a "Consistency Map" is the reworking of referential integrity from the ground up with more complete goals. Referential integrity is just a paper map; we need driving directions. A Consistent Map shows how optimistic and pessimistic consistency rules fit together. You want this map to be as small as possible - only containing actual business rules. It is a DAG like in #git; @EventModeling ensures we don't encode circular references. This is a much more important concept than event schemas in distributed #EventDriven systems where everyone leaves out temporal aspects of dependencies. With this map we don't over-engineer by relying on technical constructs like correlation and causation IDs embedded in metadata - yes, it should feel dirty to use those in your business logic. And yes, you should throw out your enterprise patterns books out; they're build walls between business and tech this way. Those concepts, if important, don't belong in metadata. Instead, we should walk actual data points that the workflows use. AND "old data" is no longer a mystery reason for why a precondition exists or how it manifested; #EventSourcing is REQUIRED for explicitly enforcing business rules properly; state is not enough. To really get there, we need to write our own indexes, collaboratively. RDBMS and current-state-only data management buries these concepts far from a collaborative level for tech and business sides.

We only do projects that have an @EventModeling diagram so clients get exactly what they want. 🥲

The game is not better predicting the future, but better adapting to how the present is different from your expectations.

#NoEstimates post with data! This team has been very predictable (items completed per day) since last November (2022). In August 2023, their Median was 7 (same) and their 90% line was at 15 (15 or less items done with 90% confidence). Predictable with #NoEstimates!

Dans le cadre d'une série de 8 articles pour nous sensibiliser sur l'ecocode et l'ecoconception. Je viens de publier un premier article sur le Green Coding. N'hésitez pas à faire lire pour faire des feedbacks à fin de mieux faire la prochaine fois. medium.com/just-tech-it-n…

You're only getting a fraction of the benefits of @EventModeling if you still find yourself using the regular ceremonies and tools in your organization. EM was designed to remove 90% of the other tooling and process so you could use 90% of your time designing & building instead.

Do we need individual component testing tools? Tools like @Cypress_io and @playwrightweb are building in component testing, is there still value in using tools like @fbjest? Here's @kentcdodds answer from today's @TestAutomationX buff.ly/3mRoZdj What do you think?

My book, Software Estimation Without Guessing, is included in @pragprog Spring Sale this week. Now is your chance to get this book (or any of 7 others) at a 50% discount. pragprog.com/promotions/

No. Our acceptance tests are indistinguishable from unit tests. Just make state views that tell you if you've met the goals of an epic.

Avis à nos experts #IT, si on vous dit "Behaviour Driven Developement", vous pensez à... La #programmation pilotée par le comportement ! Nicolas vous en parle sur #JustTechIT ➡ bit.ly/3Dh0WK6 #BDD #AXAGuildeDev

@adymitruk It would be nice to have your feedback about our usage of the fine practice

But I would correct the couple of mistakes on that event model :)

Wow. It's nice to see.

12 Powerful Visuals About Psychology & Philosophy (All Visuals are owned by quotedvisually | Hannah Wilson) 1.

If you missed @CLCondron giving his talk on Data Modelling in an Event-Centric World, fear not! It's on-demand: eventsto.re/3fbOEJK

Belle démonstration de qu'on peut faire sur du code Legacy en vue de le récrire #CleanCode @AXAJobs_fr #RaiseTheBar @AxaWebcenter qualitycoding.org/wrangle-legacy…

Co-construction : l’Event-Modeling l’outil miracle par Benjamin Seillier link.medium.com/srpa6Wosurb @EventModeling #AXAGuildeDev @AXAJobs_fr

à mort les specs, vive la doc? @VerdiereVincent @Pierre_ech #AgiLille #AXAGuildeDev @NordAgile @AXAJobs_fr

En utilisant SEEM de @estherderby @TotherAlistair nous montre que l’on peut combiner theory X et Y et donner de la direction tout en étant host et invité #Agilille2022

A 14h, on vous parle d'une des valeurs du manifeste Crafts avec @VerdiereVincent a l'#AgiLille @AXAJobs_fr @NordAgile @descampsf @Sarah__Matias #AXAGuildeDev #AXAGuilDEv

Comment faire un bon logiciel? Avec des développeurs heureux... #AgiLille #AXAGuildeDev @NordAgile @AXAJobs_fr