0009 retweeted
🚨Guys je vous demande de partager 🙏🏻
J’ai officiellement lancé une entreprise locale de fabrication de supports pour Starlink 🇸🇳
Pourquoi ? Parce que les supports vendus sur le site sont souvent chers et peu accessibles.
Notre solution : des supports solides, adaptés à nos réalités, à un prix beaucoup plus abordable.
✔️ Tu économises de l’argent
✔️ Tu soutiens une initiative 100% sénégalaise
✔️ Tu participes à la création d’emplois locaux
On construit des solutions ici, pour nous.
Intéressé(e) contacter moi inbox 📥
🤖 Made with AI
0009 retweeted
🚨 do you understand what Karpathy just said..
the guy who co-founded OpenAI.. led AI at Tesla.. one of the best engineers alive..
built an app with AI.. and said the code was the easy part..
the hard part was Stripe.. auth.. DNS.. databases.. deploying it.. connecting 15 different services that all have different dashboards and different docs and different billing pages..
AI can write your entire app in 20 minutes.. but it still can't click "confirm email" on Vercel..
so the thing that's "replacing developers" can't do the thing developers actually spend 80% of their time doing..
vibe coding didn't kill software engineering.. it just proved that coding was never the job.. the job was dealing with the mess around the code.. and that mess is still 100% human.
When I built menugen ~1 year ago, I observed that the hardest part by far was not the code itself, it was the plethora of services you have to assemble like IKEA furniture to make it real, the DevOps: services, payments, auth, database, security, domain names, etc...
I am really looking forward to a day where I could simply tell my agent: "build menugen" (referencing the post) and it would just work. The whole thing up to the deployed web page. The agent would have to browse a number of services, read the docs, get all the api keys, make everything work, debug it in dev, and deploy to prod. This is the actually hard part, not the code itself. Or rather, the better way to think about it is that the entire DevOps lifecycle has to become code, in addition to the necessary sensors/actuators of the CLIs/APIs with agent-native ergonomics. And there should be no need to visit web pages, click buttons, or anything like that for the human.
It's easy to state, it's now just barely technically possible and expected to work maybe, but it definitely requires from-scratch re-design, work and thought. Very exciting direction!
0009 retweeted
Dennis Ritchie created C in the early 1970s without Google, Stack Overflow, GitHub, or any AI ( Claude, Cursor, Codex) assistant.
- No VC funding.
- No viral launch.
- No TED talk.
- Just two engineers at Bell Labs. A terminal. And a problem to solve.
He built a language that fit in kilobytes.
50 years later, it runs everything.
Linux kernel. Windows. macOS.
Every iPhone. Every Android.
NASA’s deep space probes.
The International Space Station.
> Python borrowed from it.
> Java borrowed from it.
> JavaScript borrowed from it.
If you have ever written a single line of code in any language, you did it in Dennis Ritchie’s shadow.
He died in 2011.
The same week as Steve Jobs.
Jobs got the front pages.
Ritchie got silence.
This Legend deserves to be celebrated.
0009 retweeted
Someone builds a project management tool with Claude Code over a weekend. Ships it. Tweets "just replaced Jira."
The app works. One user, happy path, localhost. Then two people edit the same record simultaneously, and the data is silently corrupted. They don't know what an optimistic lock is. They never needed to before.
The prototype is maybe 1% of what makes software actually work. The other 99% is what you find after real users show up: race conditions, failed transactions, sessions expiring at the wrong moment, a payment webhook that fires twice and charges someone double. AI didn't cover any of that. It built exactly what you asked for.
And the confidence is the worst part. "Just need to adjust a few things before we go live." The few things you need to adjust are the product. That's like laying a foundation and telling people you basically built the house.
Vibe coding works. For personal tools, throwaway scripts, and prototypes you'll never put in front of paying users, it's genuinely fast and good enough. I use it. But there's a hard ceiling, and it shows up the moment the stakes get real.
Agentic engineering is a different discipline. You're not prompting for code. You're decomposing problems, designing system boundaries, writing specs precise enough that the agent doesn't go sideways. You review everything it builds, because it will make mistakes that only look wrong if you know what correct looks like. You guide it. You catch what it misses.
If you don't know what a distributed transaction is, the agent won't save you. It'll generate something broken with complete confidence, and you won't know until production.
The hard part of software was never writing the first 200 lines.
It never was.
0009 retweeted
Most backend engineers are used to thinking that their job ends once they provide the API endpoints.
But the real question is how well do those endpoints perform when a large number of users hit them repeatedly at the same time? And more importantly, how do you test that during the development phase?
In the video above, I explain how engineers can properly test whether their endpoints can handle scale and repeated requests from multiple users simultaneously, using a tool called Apache JMeter.
The video walks through everything—from installation to running the tool and finally testing your API. For this demo, I used a local service running on my laptop.
Do well to watch, like, retweet, and bookmark so others can learn from it too.
0009 retweeted
Certains pensent qu’on devrait cacher ce qu’on fait… moi je pense qu’on doit montrer.
On vient du même endroit, je ne suis pas plus intelligent que vous. j’ai juste osé.
Ma fierté : voir des jeunes commencer à fabriquer des choses en nous regardant construire nos drones.
0009 retweeted
Liste des livres recommandés par les invités @Thinker_View
ici : github.com/Killkitten/Thinke…
ou ici : docs.google.com/spreadsheets…
(merci à leurs auteurs)
youtube.com/watch?v=aGunIlPr…
0009 retweeted
I’m so glad I released Karmageddon. Against all odds it’s making its way into the world. If there’s one thing I’ve learned, it’s that embracing your full authentic self is the most liberating act of love.
Speaking out truth even when forces come against you is far more rewarding than silencing your integrity. Happy new year and love to you for this new and abundant year.
#truth #freedom #freespeech #liberation #viral #viralvideo
🎹 @danny_duke 🎥 @thurston_photo
0009 retweeted
Replying to @DanielLockyer
Yeah it's interesting to see all the pricing next to each other:
0009 retweeted
Alors je me lance dans cet essai… ☺️. Excusez moi les maladresses 🙂.
𝐞ⁱˣ = 𝐜𝐨𝐬(𝐱) + ⁱ𝐬𝐢𝐧(𝐱) spirituellement parlant 🌚
- 𝐞ⁱˣ : La continuité et l’élévation spirituelle, une croissance exponentielle qui rappelle les « Voies d’Ascension » mentionnées dans la Sourate Al-Ma’arij (70:3), où l’on aspire toujours à s’élever vers Dieu par l’adoration et les bonnes actions.
- 𝐜𝐨𝐬(𝐱) : La dimension horizontale, symbolisant les relations humaines et nos interactions quotidiennes avec le monde physique. Comme le mentionne le Coran :
“𝘈𝘥𝘰𝘳𝘦𝘻 𝘈𝘭𝘭𝘢𝘩 𝘦𝘵 𝘯𝘦 𝘓𝘶𝘪 𝘢𝘴𝘴𝘰𝘤𝘪𝘦𝘻 𝘳𝘪𝘦𝘯, 𝘦𝘵 𝘢𝘨𝘪𝘴𝘴𝘦𝘻 𝘢𝘷𝘦𝘤 𝘣𝘪𝘦𝘯𝘷𝘦𝘪𝘭𝘭𝘢𝘯𝘤𝘦 𝘦𝘯𝘷𝘦𝘳𝘴 𝘷𝘰𝘴 𝘱𝘢𝘳𝘦𝘯𝘵𝘴, 𝘭𝘦𝘴 𝘱𝘳𝘰𝘤𝘩𝘦𝘴, 𝘭𝘦𝘴 𝘰𝘳𝘱𝘩𝘦𝘭𝘪𝘯𝘴, 𝘭𝘦𝘴 𝘱𝘢𝘶𝘷𝘳𝘦𝘴, 𝘭𝘦 𝘷𝘰𝘪𝘴𝘪𝘯 𝘱𝘳𝘰𝘤𝘩𝘦, 𝘭𝘦 𝘷𝘰𝘪𝘴𝘪𝘯 𝘦́𝘭𝘰𝘪𝘨𝘯𝘦́, 𝘭𝘦 𝘤𝘰𝘭𝘭𝘦̀𝘨𝘶𝘦, 𝘭𝘦 𝘷𝘰𝘺𝘢𝘨𝘦𝘶𝘳 𝘦𝘵 𝘤𝘦𝘶𝘹 𝘲𝘶𝘪 𝘴𝘰𝘯𝘵 𝘴𝘰𝘶𝘴 𝘷𝘰𝘵𝘳𝘦 𝘳𝘦𝘴𝘱𝘰𝘯𝘴𝘢𝘣𝘪𝘭𝘪𝘵𝘦́.” (Sourate An-Nisa, 4:36).
- 𝐬𝐢𝐧(𝐱) : La dimension verticale, représentant notre connexion spirituelle avec Dieu, l’élévation vers le divin à travers la foi et l’adoration. Le Coran dit :
“𝘈̀ 𝘓𝘶𝘪 𝘮𝘰𝘯𝘵𝘦𝘯𝘵 𝘭𝘦𝘴 𝘣𝘰𝘯𝘯𝘦𝘴 𝘱𝘢𝘳𝘰𝘭𝘦𝘴, 𝘦𝘵 𝘐𝘭 𝘦́𝘭𝘦̀𝘷𝘦 𝘩𝘢𝘶𝘵 𝘭𝘦𝘴 𝘣𝘰𝘯𝘯𝘦𝘴 𝘢𝘤𝘵𝘪𝘰𝘯𝘴.” (Sourate Fatir, 35:10)
- ⁱ : L’aspect mystique et invisible, évoquant ce qui dépasse notre compréhension matérielle. Le Coran parle souvent du monde invisible, par exemple :
“𝘐𝘭 𝘤𝘰𝘯𝘯𝘢𝘪̂𝘵 𝘤𝘦 𝘲𝘶𝘪 𝘦𝘴𝘵 𝘥𝘦𝘷𝘢𝘯𝘵 𝘦𝘶𝘹 𝘦𝘵 𝘤𝘦 𝘲𝘶𝘪 𝘦𝘴𝘵 𝘥𝘦𝘳𝘳𝘪𝘦̀𝘳𝘦 𝘦𝘶𝘹, 𝘢𝘭𝘰𝘳𝘴 𝘲𝘶’𝘦𝘶𝘹-𝘮𝘦̂𝘮𝘦𝘴 𝘯𝘦 𝘭𝘦 𝘤𝘰𝘮𝘱𝘳𝘦𝘯𝘯𝘦𝘯𝘵 𝘱𝘢𝘴.” (Sourate Ta-Ha, 20:110)
Cela symbolise la foi en ce qui est au-delà du visible et accessible par la compréhension divine.
0009 retweeted
Pourquoi Secteur bi dafay am terrain nieup difa football ak treun gratos après niou defko Synthétique di fayekou pour Football ?
Kou mom terrain bi ?
0009 retweeted
Replying to @aissatandiathie @mountcisse
Peut être devrons nous poser la question , quelle proportion d’effectifs a besoin une presse par rapport à une population , une cible donnée. N’y a-t-il pas trop d’organes pour peu de lecteurs , consommateurs, instruits ? Et par dévers , faire du journalisme un curriculum …
0009 retweeted
Thanks to a new feature in Spring Framework 6.2.0 M5 we now support rendering multiple fragments. This is especially helpful when combined with HTMX. In this example when I remove a product from the cart the products list and order summary are both updated without JavaScript 🤯
0009 retweeted
Replying to @mutulay @SeydiGassama
L’ intérêt du rapprochement avec la Russie pour quiconque est du au fait qu’ils sont les seuls à avoir la puissance de feu à s’ immuniser contre les déstabilisations militaires qui font la persistence de la francie et de l’ otan dans les territoires africains . Gbagbo , Kadhafi






























