How I designed and built InfraFlow, an Internal Developer Platform spanning a visual workflow studio, GitOps deployment, and full observability
Every one of these was avoidable, and every one of them taught me more than the successful deploys did.
Type-safe client routing versus a full-stack framework's file-based routing — they're not really competing for the same job.
Both are real Postgres. The decision isn't about the database — it's about who you want managing auth, backups, and 3am incidents.
Not every React project needs a meta-framework. Here's a practical decision framework, not a popularity contest.
How a frustration with existing internal developer platforms turned into InfraFlow, and what building it end to end actually taught me.
Most classmates were picking between frontend and backend. Here's why I picked the layer underneath both, and don't regret it.
Running client work, coursework, and a personal flagship project in the same semester without any of them quietly failing.
Splitting an internship across DevOps and full-stack work in the same 60 days taught me more about how the two connect than either alone would have.
A minimal, repeatable self-hosting stack for small client sites — automatic HTTPS, easy multi-project hosting, no cloud platform lock-in.