Cloudflare just saved our asses again 😭🙏
PHP2Shell: two critical PHP vulnerabilities, 9.2/10 severity.
Cloudflare already rolled out emergency WAF protection, even for FREE users.
No extra charge. Just protection.
Cloudflare is literally the guardian angel of the internet 🐐❤️
W Cloudflare.
You don't need a PhD in a topic before you can start doing it. You don't need to watch 10 YouTube videos, 20 podcasts, and read 5 books before you start.
That only gets you stuck in a cycle of mental masturbation and feeling like you never know enough.
Most people should start learning only after they've started doing the thing.
How the fuck did I not know about https://t.co/4L70ZjBTj0 🤯
So many nice small animations that just make your UI feel better.
In a world where everybody is shipping AI slop, these little details are what makes your product stand out.
Given you’re not using purple gradients and putting borders around every single box of course.
@jerryjohnthomas@VirSanghavi13 Usually staging is a close replica of prod. Even if it's an exact copy of prod db, both dbs can still drift apart unless you have a setup to periodically update the staging db with prod data.
I feel this platform aims to simplify the setup work and make ephemeral envs per PR
I used to read one research paper a week. It has been 8-9 months since I last "read" one.
I still go through papers, skimming them with AI doing the heavy lifting of understanding. It is fast, and it works, but it does not feel like "reading" because, for me, reading was about understanding a paper thoroughly.
About a year ago, I used to spend hours, sometimes days, reading, understanding, and even implementing a single paper until it finally made sense. Hence, you do not see any updates on my papershelf, even though I go through 3-4 papers a week now - more than before.
I have thought about going back to the old way. But it feels too slow now, and there are days when it feels pointless to dig that deep when the answer is just a prompt away.
I feel I "know" a lot of stuff today, but did I earn that knowledge myself? Probably not. I am not sure if I am the only one feeling this way.
Maybe this is just how learning looks now.
I have 12 years of experience working as a Principal Engineer @Atlassian and I have seen replication confuse the hell out of a lot of engineers.
It's one of the most feared topics in system design and backend interviews: replication lag, quorums, split brain, failover... you name it.
But once you internalize these 20 must-know concepts, everything clicks.
Save this thread. Read till the end.
Your future interviews and production systems will thank you.
kinda best place I still visit this day for my Kubernetes learnings ... sets the tone well for the foundation + FAFO'ing around other blogs related to K8s would be the best
it already sits 48k stars on github
https://t.co/aCxOMEBXcc
Dear GitHub,
AI is changing the contribution graph.
Issues are often the real contribution now. They define the problem, shape the solution and guide the PR.
If a GitHub Issue leads to a merged PR, the issue author should get contributor credit.
Signed,
ctate