Sabitlenmiş Tweet
use case driven
31.3K posts

use case driven
@tpierrain
VP of Tech @shodo.io .Change Agent (powered by software). Former VP of Eng in a booming scale-up. Organizer of #DDDFR #AntiColonialist #mma
Now in Lyon (France) Katılım Aralık 2009
2.4K Takip Edilen4.7K Takipçiler
use case driven retweetledi
use case driven retweetledi

Article malheureusement fleuve sur la faillite des entreprises et de l'administration française en matière de protection des données.
On peut se cacher derrière des cookie walls et un beau RGPD... le problème, c'est que notre cybersec globale est un lamentable échec et qu'elle est la plus grande menace sur vos données personnelles et votre sécurité physique.
Merci pour ce douloureux rappel Seb
Seb@seblatombe
Français
use case driven retweetledi

Bad news for Karens everywhere🙂Diverse just shipped its v1.0🎉 This .NET pico-lib was prod-ready for years but stuck at 0.10.0 — missing GenerateInstanceOf<T>()
Now it's there.Your tests can finally reflect the real world: origins, genders, ages github.com/tpierrain/Dive…
#testing



English
use case driven retweetledi
use case driven retweetledi

There is a lot of things you are touching on here. First off the feeling where you feel pulled to just keep using AI because it is just easy, is the ultimate goal of your brain. The human brain is fully wired to find efficiency and use less energy at its simplest level. You now have something that can get a desired results with a fraction of effort. A good comparative example is how no one knows anyone's phone number anymore. Your brain outsourced it to a device that has it. It doesn't have to remember those numbers anymore so it doesn't. Or why don't people go hunt their own food anymore. Some do and you certainly can but for most your brain doesn't even see it as an option anymore for obtaining calories.
The other thing you are running into which you are not alone but among some of the first people effected, to truly experience it, is running into a questioning of purpose. On average most people have morphed their perceived purpose into their work and careers. Especially people who have really put in a large effort to get where they are. You know have something that is pulling that purpose into question. Who are you now if not a skilled software engineer? What does that even mean anymore?...
Even if everything goes the most utopian route with AI eliminating the need to work to survive and we enter an age of abundance. This will be the single hardest struggle people will have; what is my purpose now?! For some it will be devastating others it will turn into something wonderful and freeing.
Sadly you can stop using AI and try and get your skill and sense of accomplishment back but the spark being lit of questioning of purpose doesn't go away once ignited. The positive part though, if you can have the patience to sit with how uncomfortable it all is you can emerge on the other side in a much better position. That looks different for everyone but there is no lack of information out there to manage through it. A transition of losing purpose happens in many forms and has happened all through history.
AI just happens to be accelerating and hitting something that will effect a greater amount of people. Maybe though this will help the world start to see that life and people's worth can be more than just the job you do and money you make.
You're are not alone and there will be more and more people in this boat with you as the next few years pass. We are truly all in this together.
English

Casier-Politique.fr répertorie tous les élus en France condamnés au pénal.
La droite et l’extrême droite au top de la voyouterie 😄
casier-politique.fr

Français

Great 20’ talk by @dexhorthy on Context Engineering for coding agents: avoiding the “dumb zone”, Research→Plan→Implement workflow, and sub-agents for brownfield codebases. Highly recommend if you’re struggling with AI on brownfield/legacy code bases. 🤩
youtu.be/rmvDxxNubIg?is…

YouTube
English
use case driven retweetledi

@tpierrain @TheCodeMan__ @BrighterCommand @mjpt777 But the pump won’t pull another message until this one is done. So async/await mostly makes you a good neighbour to other performers. Often though, they are not scaled up on the same pod, but running in a different one.
English

Some developers still think async/await makes code faster.
I thought the same when I started with #Dotnet
Then one day, our API started slowing down under load.
Not because of the CPU.
Not because of the database.
Because we were blocking threads everywhere.
.Result
.Wait()
Sync database calls
Sync HTTP calls
Everything worked perfectly… until traffic increased.
What many developers miss is this: Async doesn’t make one request faster.
A request that takes 400ms with sync code
will still take ~400ms with async.
The real difference is what happens to the ThreadPool.
With synchronous code:
Thread → waits for HTTP → waits for DB → waits for I/O
The thread is blocked the whole time.
With async code:
Thread → starts I/O → returns to ThreadPool
OS notifies completion → continuation resumes.
That single difference is what allows ASP .NET Core to handle thousands more concurrent requests.
The real killer I keep seeing in production codebases is this:
Sync-over-async
var result = httpClient.SendAsync(...).Result;
This blocks the thread again, and under load, it can lead to ThreadPool starvation.
And once that happens, your API starts feeling “mysteriously slow”.
No CPU spikes.
No database bottlenecks.
Just no threads left to process requests.
I made this visual to explain what actually happens inside ASP. NET Core.
Curious:
Have you ever debugged a production issue that turned out to be sync-over-async?
___
Join our .NET Hub (1.1k members) for free to learn more: skool.com/thecodeman-com…

English

@ICooper @TheCodeMan__ @BrighterCommand @mjpt777 What I'm not sure to get is what you mean by "when you use await you free up nothing". Is that specific to Brighter's own sync context?
Because in classical code with I/O, async/await in .NET does prevent the thread from blocking, right?
English

@ICooper @TheCodeMan__ @BrighterCommand Hello Ian, I get the "an efficient single thread can outperform parallelism & concurrent threads" (something I discovered long time ago while working on low latency systems in finance + @mjpt777 tremendous work on the disruptor pattern & more: #_overview" target="_blank" rel="nofollow noopener">lmax-exchange.github.io/disruptor/disr… )
English

⚡“Marty, il faut retourner à Devoxx France !”
Après avoir voyagé dans le temps à Devoxx Belgium 2025, @JulienTopcu et moi remontons sur scène pour livecoder le découpage d’un monolithe en une ruche puis en microservices avec le pattern the Hive 🐝
Pour♥️:m.devoxx.com/events/devoxxf…




Français
use case driven retweetledi

🚨 Chrome Gemini Vulnerability Lets Attackers Access Victims' Camera and Microphone Remotely
Source: cybersecuritynews.com/chrome-gemini-…
A high-severity security vulnerability has been discovered in Google Chrome's integrated Gemini AI assistant, exposing users to unauthorized camera and microphone access, local file theft, and phishing attacks, all without requiring any user interaction beyond launching the browser's built-in AI panel.
Tracked as CVE-2026-0628, the flaw resided in how Chrome handled the declarativeNetRequest API, a standard browser extension permission that allows extensions to intercept and modify HTTPS web requests and responses. This API is widely used for legitimate purposes, such as ad-blocking.
#cybersecuritynews

English
use case driven retweetledi

Rien n’aura été épargné aux iraniens en lutte pour la démocratie. Il leur faut donc choisir leur façon de mourir ? La corde et les balles du dictateur ou les bombes de Trump et de Netanyahu ? Et il nous faudrait accepter - sans broncher - cette idée folle qu’il n’y aurait « aucune alternative » ? Qui décide de cela ? Pas d’autre issue, vraiment, que la mort ou la mort ? Le digne peuple d’Iran n’est pas chair à canon. Les civils ont le droit de vivre, et libres. Il faut les y aider urgemment. Pas les tuer. Reste-il encore des démocrates lucides en ce monde ?
Français
use case driven retweetledi







