Antoine Alberti

@antoinealberti
61 Followers
62 Following
2.6K Posts
Dev, socio-poetical anarchitect, agile/lean evangelist under cover, grey areas researcher, self-certified itDependser and rubberDucker
I can name things and invalidate caches
coach & trainer @ arolla
blogblog.antoinealberti.com

Examples of sharing conclusions in retros vs sharing observations:

Conclusion: "we need more code review"

Observation: "we released a customer impacting bug last week, and a few others in the weeks before"

When we use retro templates like start/stop/continue, they invite folks to jump to conclusions before the group discusses. Folks who don't like the conclusion can either argue a contrary position or ignore the comment -- neither the aggressive confrontation nor the silent ignoring are good for teamwork.

When we use retro templates like liked/learned/lacked, they invite folks to share their experience, observations, and feelings. Then the group works together to understand what's happening and come up with a conclusion (and action) together. Often other folks share additional insights or data before we come to a conclusion. Even if they don't, when we come to a conclusion together, we have a shared ownership, and we know why we're taking the action (instead of "because so and so said to").

Notes from a conversation with a friend about how to build trust and candour within a team at work:

- The more frequent the retrospectives, the better: 18 minutes per day does much more to build trust than 90 minutes once per week
- You can take the lead in sharing vulnerably in a retrospective. If you're respected, it gives others confidence. If you're disrespected, now you know who is hurting the team safety, and you have a specific example you can bring up in a 1:1
- In the retrospective, push for specifics. Folks who are shy may get vague in their comments as a way to avoid confrontation. This is good for social cohesion in a ruinous empathy sort of way. By pushing for specifics, you can bring the conflict into the open so we can work through it
- It may help to have an active facilitator to help make the retrospectives productive
- If you share observations and feelings instead of conclusions, you invite discussion and are likely to come up with more suitable and actionable conclusions

Be the elephant you wish to see in the room.
If we are destined to anything, it's to navigate in uncertainty
douglas adams's story about the civilization that built a giant computer that gave the ultimate answer but nobody knew what the question was so they put all their resources into building an even bigger computer just to figure out the question ... it feels more plausible every day.
I came up to calling AI The Hunger. Pretty much sums it up, after all
The only thing I expect from an estimate is its cheapness. So I do them real cheap. Pick a number. Good enough.

Trying to put my hands on agentic dev at a professional level. I'm at the point where it's either so easy I could have done it quicker by hand, or a bit more complicated, and I finish by hand when the beast is lost. Not sure I'm saving time, so far.

I suppose I need to learn getting somehow softer on my requirements, as I'm not the one coding anymore.

Anyway, I can't really claim I tamed the World Eater, so far.

"A study of physicians in Poland who specialize in endoscopy — the use of flexible probes to examine the inside of the human body — shows how quickly AI tools can erode human abilities. The physicians, who had all performed at least 2,000 colonoscopies during their careers, were given access to an AI system that analyses colonoscopy images in real time and flags a type of precancerous intestinal lesion called an adenoma. The tool was available to the specialists on some days but not on others.

Once physicians began using it, their performance dropped significantly whenever the system was unavailable. During the three-month period before the AI tool was introduced, the specialists found at least one adenoma during 28.4% of colonoscopies. During the three-month period after the tool was introduced, the adenoma detection rate for colonoscopies performed without AI assistance decreased to 22.4%.

Gastroenterology and Hepatology, suggest that even highly skilled professionals might get worse at tasks that their job requires as they become more dependent on AI tools, says Robert Wachter, a physician at the University of California, San Francisco, who is the author of a book on how AI tools are transforming health care. The study authors say that continuous exposure to such tools can cause clinicians to become “less motivated, less focused, and less responsible when making cognitive decisions without AI assistance”.

Co-author Yuichi Mori, a physician-researcher at the University of Oslo, says that more studies are needed to confirm the phenomenon. But people who use AI tools should be aware that they risk losing some of their skills, he adds. “There is no established solution against deskilling right now. It should be a very hot research topic in the next decade.”"

https://www.nature.com/articles/d41586-026-01947-1

#AI #Deskilling #Science #Medicine

Is AI ruining our skills? Early results are in — and they’re not good

Reliance on artificial-intelligence tools degrades the abilities of physicians and software engineers, studies show.

In the small, bounded, separable: perfection is beautiful.

In the wide, in the dependent and the depended-on,
perfection is a flaw.