Code, cadence, cold brew ☕ Laravel developer · Quran recitation teacher
Bahrain
Joined June 2009
- Tweets5.7K
- Following997
- Followers1.3K
- Likes353
10x 20x 50x😹
remember when hosting companies sold us bandwidth like it was gold?
tokens r th nw bandwidth.. these limits will eventuallybcom boring 🥱
real problem? we hv bcom addicted to instant results💀
#PHP 8.6 is getting closer.
Meanwhile some #developers are still explaining why PHP is dead for the 19th consecutive year 😹
At what point do we judge a language by what it delivers instead of its reputation?
Not everything needs #Redis
Sometimes query already fast/ data barely changes
caching just creates another problem to debug 😂
GitHub recently shipped agentic autofix for code scanning alerts..
The question is whether automating fixes also means automating confidence 😅
Thinking of launching your first website? 🚀
Here’s 20% off #Hostinger for your first purchase!
hostinger.com/?REFERRALCODE=…
Full disclosure: It’s my referral link so I earn a commission too Win-win! 😄
Valid for new Hostinger customers only
sometimes boring technology is smartest decision
Not everything needs to be modern.. Some things just need to work!
Mohamed Marhoon retweeted
php vulnerabilities: time to clarify what really happened
here's my conversation with @derickr, a member of php internals. we go through the full timeline and the facts
watch here: youtu.be/5X5csEbmHqs?si=uAk7…
Security rule #1 Data you never collect can never leak
Rule #2 encryption great but if your app and db share same keys hackers might get whole combo meal 🔥
Less data.. fewer secrets.. smaller blast radius
even #hackers appreciate clean architecture 😂
it’s 2026. build like you’re already going to get hacked, because sooner or later you probably will
collect less. only keep the customer data you actually need. anything you never store can’t leak
encrypt everything you keep. not just passwords and card numbers: names, emails, addresses, photos, uploads, all of it. if someone gets into your database or storage, they should find nothing they can read
delete what you don’t need anymore. old accounts, expired orders, stuff from years ago that nobody uses. set it up so it gets deleted automatically, not “someday"
don’t store tokens or api keys unless you really really really really have to. if you do, encrypt them hardcore or put them in a secrets manager. and either way, keep your encryption keys separate from the data they protect
basically: the less data you keep, the less you have to worry about when you get hacked
Mohamed Marhoon retweeted
The PHP ecosystem had a pretty eventful 48 hours.
Two critical RCE vulnerabilities (CVSS 9.2), a leaked disclosure, and emergency security patches.
But here's what really caught my attention: one of the issues had surfaced during an external audit in 2024. The PHP Foundation later described the delay in resolving it as a “structural failure.”
The good part? They're looking at changes to security decision-making and investing more in security work.
Open source isn't maintained by magic. It takes people, time and funding, especially for the unglamorous work of keeping things secure.
If you run PHP in production, check your runtime and apply the appropriate security update. Updating Composer dependencies alone won't patch PHP itself.
Hopefully, this incident leaves the PHP ecosystem stronger than before. ❤️
Huge respect to the #PHP team! ❤️
Keeping millions of applications running /secure /improving.. All for FREE!
No subscriptions just pure open source dedication
#PHP frees memory but a stale reference may still point to it
Even memory has trouble letting go 💔😂
PHP vulnerabilities discovered in 2026 may have been hiding for years
Your code passed every test.. vulnerability passed every release 😂🐘
B
The goal isn't fewer lines or more lines It's less cognitive load 😎
code written once but read and maintained countless times
