
Building Solutions with Laravel + React | Tech Enthusiast | Mail ~ [email protected]
Nigeria
Joined June 2020
- Tweets2.4K
- Following769
- Followers1.4K
- Likes13.4K
Sometimes, i envy less responsible people, they don't care about generational wealth, just vibes and Inshallah and they are happy
You see, sometimes trouble comes gently, but we are the ones who invite it in.
Your husband’s family came to you with two options: either bury their son in his own house or in his father’s house. Yet, as his wife, you insist that he must be buried in a cemetery.
Would you have preferred that he be cremated instead, since the thought of seeing his grave seems so unbearable to you?
Just tryyyyyyy, do everything you can to stay alive.
The car will not cause her trauma.
The money he left behind will not cause her trauma.
The photo frames, the videos and his media pages will not cause her trauma.
But just a little space in the compound to bury her supposed lover is now a war.
Also, there is no way a man would refuse to bury his wife in the compound.
Of course, she will definitely remarry, and maybe she will even sell the house. She knows the implication of having a grave on a property she wants to sell.
A man suffers to make it, the man dies, and he is still lying in the mortuary because his wife will not allow him to be buried in his own house.
Again, kings, please don't die!
People are choosing not to have children. Not necessarily because of expense but because it's becoming unnecessary
Nigerians are very funny, I said in a Tiktok comment section that "Solar panels perform better on lower temperatures, what generates the power is sunlight and not heat".
These people started arguing with me instead of looking up the claim. They want to argue so bad without even knowing if they are wrong or not
phprust.com
Yet another #compiled #PHP implementation. This time written in Rust. At first glance, the project looks pretty promising. So, has the future finally arrived? :)
Ayzerobug retweeted
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped.
Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲
The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough.
I can barely get two sentences into explaining my implementation plan before someone interrupts with:
“Just give it to Claude to do!”
“Sir, we need to think about…”
“That’s what Claude is there for. Let it do the heavy lifting!”
A task gets assigned, and barely 10 minutes later:
“Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!”
Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear.
Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation.
Just ship it. And ship it NOW.
AI has become both a blessing and a curse.
Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them.
We’ve made development faster, but somehow, we’ve also made every delivery feel slower.
And that’s the irony nobody seems to be talking about.
Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
Claude tries to leave a reference of the ticket we are working on in the Doc
Noo, if the business changes tasks management system tomorrow, we’ll lost context.
Document these processes right here in the code and don’t put any ticket id
Those Python boys bashing PHP yesterday, where are you?
🚨🚨🚨 ALERTE SÉCURITÉ MAXIMALE ! Python est compromis.
🔸 Mettez immédiatement pip à la version 26.2.2 ou plus.
🔸 Dans chaque projet Python (chaque venv) : python -m pip install --upgrade pip
🔸 uv : uv self update (0.13.4 ou plus)
🔸 Mettez aussi à jour les certificats du système (apt / dnf upgrade ca-certificates) et vos images Docker
pip install est compromis.
L'autorité indienne eMudhra (emSign), qui signe les « passeports » prouvant qu'un site est bien celui qu'il prétend être, utilisait des clés secrètes ridiculement faibles : 8 clés, toutes inférieures à 256. L'une valait 4. Autrement dit, n'importe qui peut fabriquer un faux passeport valide pour n'importe quel site.
Le risque pour Python : quelqu'un sur ton réseau (wifi public, FAI, État) se fait passer pour pypi.org, et ton « pip install » télécharge un paquet piégé sans aucune alerte. Aucune attaque n'a été signalée pour l'instant, mais c'est trivial à faire.
Un paquet piégé peut installer n'importe quoi. Porte dérobée, virus, vol d'informations en tout genre.
La situation est terrifiante !
Rien que dans l'écosystème Python, chaque installation de CPython, chaque venv, uv, tout est exposé.
Et je ne vous parle même pas de npm, pnpm, yarn, Go, Rust.
Ma stratégie de sécurité 2026 : rester chez moi et ne me connecter à Internet que depuis un FAI de confiance.
C'est quand il y a de la mer qu'on reconnaît les vrais marins...
Readers added context they thought people might want to know
Ce n'est pas un bug Python mais une vulnérabilité des clés privées faibles des certificats intermédiaires eMudhra/emSign (d<256 dont une valant 4), exposant les bundles certifi/pip à des MITM TLS potentiels jusqu'aux mises à jour.
discuss.python.org/t/information-…
emudhra.we-have-a-problem.com
scotthelme.co.uk/eight-bits-of-…
github.com/advisories/GHS…





















