Dipanda Aser

Software Engineer
Golang, Elixir, Nodejs, Adonisjs,
Svelte & Kit, Windev (PcSoft)
Contributor at @osscameroon

Building @muleta_dev

[Dipanda Aser @iamdipanda]

Hey folks,
Je viens de créer https://t.co/6UqyFeuXYt .

Dans cette toute première version c'est juste une API qui permet de rechercher des médicaments autorisés au Cameroun.

Les data viennent de https://t.co/Zb5XcxseNg

Source: https://t.co/FBF5BgANDF

[BillyJov @billyjov_]

Existe-t-il une API qui retourne une liste des medicaments prescrits et commercialisés au cameroun/en afrique? Ou une méthode pour me procurer ces informations par script?

Le maroc a par exemple https://t.co/POV5E958C4

#CaParleDev

CC: @yopafabrice @Boris_Gauty

[Romain Lanz @romainlanz]

Au vu des dernières supply-chain attaques, il y a une dernière étape que vous pouvez ajouter si vous êtes dans l'écosystème JS, Python ou Rust (en plus de tout ce que j'ai déjà cité dernièrement).

Mettre un firewall devant votre package manager 🔐

Socket Firewall analyse les packages avant installation et peut bloquer automatiquement des comportements suspects ou connus comme malveillants.

[Dipanda Aser @iamdipanda]

Hey Guys, i started working on this open source project that might be helpful for others out there.

It's an open source bull mq dashboard and toolkit to help developers have a perfect view of what going on in their background job

i have a demo here: https://t.co/VLAsYwi6LW

[Dipanda Aser @iamdipanda]

Don't ship background job you can't see.

i've been the on-call engineer trying to have a clean observable view of what's was going on with some successive failures on a system. but the tools i was using couldn't fit the work i wanted into the scope.
So i built @muleta_dev 📍

[Dipanda Aser @iamdipanda]

links:

– npm i @muleta-dev/server
– https://t.co/iwlpZVf84Y
– https://t.co/dxEEWnh7F6

I'll end this thread with my favorite quote since i started working on muleta: " don't ship background jobs you can't see "

[Dipanda Aser @iamdipanda]

Don't ship background job you can't see.

i've been the on-call engineer trying to have a clean observable view of what's was going on with some successive failures on a system. but the tools i was using couldn't fit the work i wanted into the scope.
So i built @muleta_dev 📍

[Dipanda Aser @iamdipanda]

here's a live demo populated with synthetic queues / schedulers / flows.
click everything, retry stuff, pause queues. redis is volumeless and the data is fake, so you can't really break it.

👉 https://t.co/VLAsYwi6LW

[Valery Melou @valerymelou]

🏆 The first ever Builderswave Product of the Week is...

Cay Vay by @AlbanTyrex 🇨🇲.

Cay Vay builds resumes that get people hired. And when it came time to vote, the people it got hired showed up.
There's no better validation for a product than that.

Out of 10 products competing in the very first launch week, the community spoke clearly.

Alban, you didn't just win a competition. You won the first one. That's a permanent thing, no matter how big Builderswave gets, week 1, product 1, will always have your name on it.
Congratulations. You earned it. 🙌

To the other builders who competed, thank you for being first. You took a chance on a platform that didn't exist two weeks ago and you made this real. The wave wouldn't have started without you.

Week #2 is ongoing now. Let's keep the momentum!

👉 https://t.co/xVKmNhsUjQ

[CG @cgtwts]

“who should we lay off first”

CEOs:

[Dipanda Aser @iamdipanda]

Shipped v0.1 of muleta this week open-source dashboard for BullMQ.
Polishing the demo this weekend. real launch tuesday. if you run BullMQ @bullmqhq in prod, my DMs are open and i'd love to know what existing dashboard doesn't do for you.

https://t.co/iwlpZVf84Y
@muleta_dev

[Dipanda Aser @iamdipanda]

@valerymelou @muleta_dev Just did it

[𝑺𝒊𝒏𝒊𝒄𝒂✨WISHLIST TINY DELIVERY @artem_sini39436]

Tiny Delivery Official Trailer is here!🌿
#gamedev #indiegame #cozygame

[Wil Aime @WilAime]

Re

[Wil Aime @WilAime]

C’est officiel. WHO
Au cinéma à partir du 26 mai 2026.

Bon, je vais essayer de ne pas être trop long, mais ça ne va pas être facile 😭

Je suis très fier et ému de pouvoir enfin vous présenter mon premier long-métrage, produit en totale indépendance.
Avec toutes les redoutables difficultés que ça implique, mais aussi avec la liberté rare et enivrante que ça permet.

Je m’étais promis de tout tenter pour créer quelque chose à grande échelle, sans jamais trahir nos codes, notre manière de raconter, et notre instinct. Aujourd’hui, je suis fier de ne pas avoir lâché cette promesse parce qu’au fond, ce film est aussi une preuve que c’est possible, quand on y met tout son cœur, son âme et son esprit.
En réalité, il a fallu bien plus que ça : du temps, de l’énergie, des doutes, des sacrifices. Et surtout, une équipe incroyable, portée par la foi, le courage… et peut-être un peu de chance aussi.

Beaucoup de celles et ceux qui ont travaillé sur ce film portaient déjà quelque chose en eux : du talent, une vision, une envie. Mais pas toujours l’espace pour l’exprimer à cette échelle. Alors on l’a construit cet espace. Étape après étape. Jour après jour. Ensemble.

#WHO sortira au cinéma en France, dans toute l’Afrique francophone, au Canada, et ailleurs. (AVP mondiale au Grand Rex le 26/05/26)
C’est encore difficile à réaliser, mais on l’a vraiment fait, et à notre manière. Avec nos règles et notre vision.

Merci à toutes celles et ceux qui font partie de cette aventure depuis des années, qui m’ont fait grandir et qui ont grandi avec moi.

Merci à toutes celles et ceux qui ont embarqué en route, et à toutes celles et ceux qui embarqueront.

Merci à toutes celles et ceux qui ont gardé la foi. Celles et ceux qui l’ont perdue, et qui l’ont retrouvée.

Du fond du cœur, merci.

On va enfin pouvoir commencer.

Wil

[𝑺𝒊𝒏𝒊𝒄𝒂✨WISHLIST TINY DELIVERY @artem_sini39436]

It's been:
10 months since the idea
7 months since the prototype
2 days until until the announcement!

I’ll Deliver smth new soon🏁

[kyutai @kyutai_labs]

We're releasing Hibiki-Zero, a new real-time and multilingual speech translation model that can translate 🇫🇷French, 🇪🇸Spanish, 🇵🇹Portuguese and 🇩🇪German to English: accurate, low-latency, high audio quality, with voice transfer. And best of all: open-source.

[Marc @MarcJSchmidt]

All my new code will be closed-source from now on. I've contributed millions of lines of carefully written OSS code over the past decade, spent thousands of hours helping other people. If you want to use my libraries (1M+ downloads/month) in the future, you have to pay.

I made good money funneling people through my OSS and being recognized as expert in several fields. This was entirely based on HUMANS knowing and seeing me by USING and INTERACTING with my code. No humans will ever read my docs again when coding agents do it in seconds. Nobody will even know it's me who built it.

Look at Tailwind: 75 million downloads/month, more popular than ever, revenue down 80%, docs traffic down 40%, 75% of engineering team laid off. Someone submitted a PR to add LLM-optimized docs and Wathan had to decline - optimizing for agents accelerates his business's death. He's being asked to build the infrastructure for his own obsolescence.

Two of the most common OSS business models:
- Open Core: Give away the library, sell premium once you reach critical mass (Tailwind UI, Prisma Accelerate, Supabase Cloud...)
- Expertise Moat: Be THE expert in your library - consulting gigs, speaking, higher salary

Tailwind just proved the first one is dying. Agents bypass the documentation funnel. They don't see your premium tier. Every project relying on docs-to-premium conversion will face the same pressure: Prisma, Drizzle, MikroORM, Strapi, and many more.

The core insight: OSS monetization was always about attention. Human eyeballs on your docs, brand, expertise. That attention has literally moved into attention layers. Your docs trained the models that now make visiting you unnecessary. Human attention paid. Artificial attention doesn't.

Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. Most popular OSS runs on economic incentives. Destroy them, they stop playing.

Why go closed-source? When the monetization funnel is broken, you move payment to the only point that still exists: access. OSS gave away access hoping to monetize attention downstream. Agents broke downstream. Closed-source gates access directly.
The final irony: OSS trained the models now killing it. We built our own replacement.

My prediction: a new marketplace emerges, built for agents. Want your agent to use Tailwind? Prisma? Pay per access. Libraries become APIs with meters. The old model: free code -> human attention -> monetization. The new model: pay at the gate or your agent doesn't get in.