Software Engineer — turning "it works on my machine" into "it should 👀 work everywhere"

Website · LinkedIn · GitHub · Email

I work full-time as a software engineer, mostly working towards scalable system design, DevOps practices, and handling cloud infrastructure without praying — provisioning, automating, and scaling the plumbing so every code has somewhere to run 🤞.

I'm still a builder though. Frontend and backend are a few prompts away these days, so I don't think there's much left to brag about there.

Cloud & Infrastructure

Designing and provisioning infrastructure across AWS, GCP, Azure, and random $5 VPS; defining it with Terraform and Pulumi so I'm not second-guessing how it was put together six months later.

Containers & Orchestration

Mostly figuring out how to get things running without turning a simple application into a nightmare of launch sequences.

Kubernetes is great when you actually need it. For the average AI slop with two users who signed up yesterday, a random VPS and Docker Compose is probably already overkill. PS: they probably also logged out yesterday.

CI/CD & Automation

Building pipelines with GitHub Actions and Jenkins, automating deployments and infrastructure so shipping software doesn't require a ritual involving SSH, screenshots, and crossed fingers.

Backend & Systems

Mostly TypeScript and Python. Golang is really nice too.

Sometimes the answer is a distributed system. Sometimes it's a monolith with a bash script run by a cron job. Both have their place. One just looks better in a diagram.

Building around queues, workers, and asynchronous processing when making everything synchronous starts looking like a bad life decision.

Data

Postgres is the default.

Redis when caching or low-latency state actually needs it and Memcached or SQLite won't cut it. I'm probably not reaching for another distributed system or dependency just to feel important.

MongoDB occasionally, when the data genuinely doesn't make sense.

Frontend & UX

I've been doing a lot of infra lately, but I still like building things people actually interact with — making UI feel good, UX flows that make sense, and the product actually tell the same story.

Building with Next.js, trying to give users a sense of satisfaction rather than a panic attack while they navigate the maze the agent designed.

It gets even more interesting when optimizing the rendering cycle, fantasizing over flame graphs, and figuring out the root cause behind random memory leaks — occasionally blaming React for me being an idiot.

Currently obsessing over

Infrastructure-as-code, event-driven architecture, Kubernetes internals, and generally figuring out how to make systems fail less dramatically.

Also building monolithic AI slops, because why not.

_{probably overthinking it  ·  definitely overengineering it  ·  ships things, occasionally on time}