@celtiisbj Je suis proche du routeur @celtiis
La connexion internet est toujours aussi lente...
Je viens de payer (encore) la facture du mois. Mais je n'ai pas droit à une bonne qualité de service. Si les promesses de débit ne peuvent pas être tenues, donnez-nous au moins de la stabilité.
v1.0 is out now! 🙌
It took more than a decade, TypeORM was considered dead by many over the past years...
But since late 2024 a group of dedicated maintainers was working hard and finally shipped what so many developers were waiting for: the first officially stable version!
📣 Moneytrees is live! So proud to be able to launch my very own SaaS finally. Over the past 4,5 months I worked hard on building it. It's how I wish other invoicing software would work. Go give it a try with the free tier and let me know what you think!
I'll share more behind-the scenes stuff soon.
J’ai récemment développé une application mobile de recettes camerounaises 🍲 avec plus de 100 recettes.
Vous voulez tester l’app ? Envoyez-moi votre email en DM (Android uniquement).
Sinon, une version web est aussi disponible : https://t.co/7suVxomHzH
Le projet est open source : https://t.co/WwBr4t7W8g
Stack : Stitch + Claude 🫱🏾🫲🏽
L'infographie est bien évidemment exagérée à mort et ne doit pas être prise à la lettre
Ce qui importe pour votre sommeil c'est :
1) La régularité (toujours dormir aux mêmes heures)
2) La durée (7/9 heures dès lors que c'est possible)
3) La qualité (vous y pouvez rien)
If you use Laravel Valet and Safari feels slow on .test domains, the fix is simple.
Safari tries IPv6 first, times out, then falls back to IPv4. Just tell dnsmasq to also resolve .test to the IPv6 loopback address and restart it.
Thanks to my colleague @rubenvanassche for this one.
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you!
They say AI is the end for developers.
They say the job market is gone.
They say learning to code is pointless.
I don’t buy it.
I think we're just getting started.
I’ve been a developer for 10 years.
I’ve mastered languages. I’ve optimized databases. I’ve built systems that handle millions of requests.
But last week, a Junior dev outperformed me.
He didn’t know how to write a complex program. He couldn’t explain the difference between a proper monoloth and a microservice. He didn't even know how the code worked in some parts.
But he knew how to talk to the Agents.
He orchestrated three AI workers. One for the frontend. One for the backend logic. One for the unit tests.
In 4 hours, he pushed a feature that would have taken me 3 days.
I felt a cold shiver. "Is this it?" I thought. "Am I finally the legacy hardware?"
But then I looked at his PR. It was fast. It was functional. But it was… fragile.
It lacked architectural vision. It had security holes that only someone who has been "burned" would see. It was a house built on sand.
That’s when I realized the truth about 2026.
The "Senior" title isn't about how fast you type anymore. It's about how well you judge.
We are moving from being "builders" to being "architects." From "coders" to "composers."
If you’re a veteran feeling left behind by AI: Don’t compete on speed. Compete on wisdom.
The machine can write the notes. Only you can write the symphony.
I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit.
My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently.
So, here goes.