Lehmann Emmanuel (@thelimande) profile picture

.NET C# Sr. Developer, Software Craftsmanship Agile BDD Coach in DSI AXA France

Lille, France
Joined December 2013
Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)Photo by Lehmann Emmanuel (@thelimande)
Lehmann Emmanuel retweeted
Le marché IT ne se dirige pas vers la disparition des développeurs, mais vers une redéfinition de leur valeur. L’IA automatise une partie de l’implémentation et du code standardisé, tandis que les entreprises valorisent davantage les profils capables de comprendre un problème métier, concevoir une architecture, intégrer l’IA dans un produit, vérifier la qualité des résultats et assumer la responsabilité de la mise en production. Les intitulés émergents comme Product Engineer, AI Engineer, AI Platform Engineer ou Agent Reliability Engineer traduisent cette évolution, mais les frontières entre ces rôles restent encore mouvantes.
🤖 Made with AI
3
8
71
5,560
Albert Einstein a dit : « Tenez-vous loin des personnes négatives. Elles ont un problème pour chaque solution. »
3
10
1
40
3,202
Lehmann Emmanuel retweeted
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.
1
2
6
602
Lehmann Emmanuel retweeted
We only do projects that have an @EventModeling diagram so clients get exactly what they want. 🥲
1
11
372
Lehmann Emmanuel retweeted
The game is not better predicting the future, but better adapting to how the present is different from your expectations.
5
54
3
179
23,151
Lehmann Emmanuel retweeted
#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!
3
7
26
3,930
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-now/… – at Sucy-en-Brie, France
3
9
343
Lehmann Emmanuel retweeted
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.
2
4
15
2,029
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?
2
5
15
1,106
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/
2
18
2
74
16,202
Lehmann Emmanuel retweeted
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.
How do you write solid acceptance tests? Found it difficult to make this work FOR YOU? Many developers try but struggle to write and maintain these kinds of tests, but there is help out there! 👇 Get my FREE compact guide on ATDD with tips for success ➡️ subscribepage.com/cd-atdd-gu…
4
2
11
2,458
Lehmann Emmanuel retweeted
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 ➡ https://nitter.cf/t.co/DFBpRbt5oU #BDD #AXAGuildeDev
1
3
Lehmann Emmanuel retweeted
12 Powerful Visuals About Psychology & Philosophy (All Visuals are owned by quotedvisually | Hannah Wilson) 1.
10
958
16
4,068
Lehmann Emmanuel retweeted
If you missed @CLCondron giving his talk on Data Modelling in an Event-Centric World, fear not! It's on-demand: eventsto.re/3fbOEJK
3
1
11
Lehmann Emmanuel retweeted
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
1
4
Lehmann Emmanuel retweeted
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
7
26
Comment faire un bon logiciel? Avec des développeurs heureux... #AgiLille #AXAGuildeDev @NordAgile @AXAJobs_fr
2
1
22