Passionate Laravel Developer who thrives on coding and debugging, constantly turning challenges into opportunities for growth. An advocate for open-source, contributing to various projects and believing in the power of collaboration.
Deep interest in cybersecurity, actively contributing as a core member of communities like YAS (Yet Another Security) and InitCrew, collaborating to push the boundaries of digital security.
Exploring the fascinating world of Radio Frequency using SDR devices, blending curiosity for technology with hands-on experimentation in signal analysis and spectrum exploration.
Love giving back to the community by contributing to open-source projects. Technology inspires me in every way — a boundless world of possibilities that fuels creativity every single day.
BOLA gets all the OWASP fame for letting you peek at someone else's data. Its quieter sibling, Broken Function Level Authorization, is the one that lets a regular user call an admin endpoint directly and quietly promote themselves. Same root cause, much scarier blast radius.
Everyone reaches for \"a message broker\" like it's one thing. It isn't. Queues and pub/sub solve different problems, and picking the wrong one doesn't fail loudly — it just quietly rots your architecture for the next two years.
GitHub-hosted runners are boring in the best way. Self-hosted runners promise speed, cache locality, and cheaper minutes — and quietly hand you a fleet to patch, secure, and babysit. Here's how to tell if the trade is actually worth it.
bcrypt got us through two decades of password breaches admirably, but it has a blind spot GPUs and ASICs have been happily exploiting for years. Here's why argon2id is the actual right default now, and how to migrate without forcing a mass password reset.
Node upgrades and cluster autoscaler scale-downs are supposed to be boring. Without a PodDisruptionBudget, Kubernetes is happy to evict every replica of your app at once to get there. Here's how PDBs actually work, where they quietly do nothing, and the mistakes that turn a routine drain into an incident.
Adding a NOT NULL column feels harmless until it locks a production table mid-deploy and your API starts timing out. Here's the expand/contract pattern that lets you change a live schema without anyone noticing — except the one time I forgot step three.
