Full-stack engineer. write about things I actually built, bugs that actually hurt, and problems that took longer than they should have.
Two critical PHP vulnerabilities, one sleepless night, and AI agents making the race a lot more interesting. October 20, 2026. Imagine being a PHP developer or a sysadmin running production applicatio
Imagine two businesses running almost the same AI workflow. Same use case. Same number of customers. Same AI model. One mainly serves customers in English. The other mainly serves customers in Malayal
When developers hear “100K users”, our brain usually starts building infrastructure before the product even exists. A backend server. A database. Cloud storage for images, PDFs and uploads. CDN. Monit
I was looking at one of the most normal features you can find in almost any application: Update Profile. Nothing exciting. A user changes their name, profile picture, maybe email, and the backend upda
OTP flows make developers feel safe. They look secure. They feel secure. They even demo well. But here’s the uncomfortable part: sometimes an OTP flow can become almost useless if the actual security
As developers, we have all seen bugs caused by recursion. When recursion goes out of control, we usually expect something simple: Stack overflow → application crashes → fix the bug. But what if that s
A step-by-step guide to building an SSH server in Go that renders a TUI portfolio inside anyone's terminal hosted for free on GCP.
What happens when you treat a portfolio like an engineering problem instead of a design problem.
