Hey, I'm Meet

I'm a software engineer based in New York City. By trade, I build scalable web applications; by necessity, I'm a gym rat.

I've spent my career in the trenches of fast-paced startups, learning how to build and scale web applications at real-world scale. On this site, I share my end-to-end workflow — from designing system architecture and mapping API flows to orchestrating deployments and running live servers in production.

I hold both a Bachelor's and a Master's degree in Computer Science, but my curiosity about computers started much earlier. As a kid, I was fascinated by how a few lines of code could make machines do powerful things. That curiosity became real when I picked up C/C++ using the classic "Let Us C" book (thanks to countless Quora recommendations). Back then, coding meant Turbo C, and it was genuinely fun.

Around 2018, I pivoted into the world of web development as the ecosystem began to explode. Once I started learning JavaScript, there was no turning back. I focused heavily on strengthening my fundamentals and eventually went deep into the React ecosystem, working with React, Node.js, and TypeScript to build modern, scalable applications.

I completed my Bachelor's degree in 2021 and went on to work with a few fast-paced, funded startups, including:

Pipehaul, KeepWorks, and DashX.

These experiences were foundational. I learned how to ship products from the ground up, why clean and maintainable code matters, and how to deliver features under tight deadlines without sacrificing quality.

Today, I specialize in full-stack development, architecting applications using TypeScript, Next.js, AWS, Prisma ORM, and PostgreSQL.

What I Work With

TypeScript
Next.js & React
Node.js / NestJS
PostgreSQL & Prisma ORM
AWS
GraphQL & REST APIs

I also rely on modern tools like Cursor, Claude, and Linear to move fast while keeping quality high.

How I Work

I default to shipping fast and iterating. Not reckless — just biased toward getting something live early and improving from there rather than perfecting in isolation.

A few things I'm consistent about:

Deploy on day one. Even a blank page. Real environments catch real problems.
Boring code over clever code. Readable, predictable, easy to delete.
CI breaks the build or it doesn't count. Lint, type-check, build — all enforced, no exceptions.
Write before you talk. Async by default. If it's not written down, it didn't happen.
README before code. Forcing clarity on paper before writing a single line.

Writing

I write about engineering, tooling, and how I think about building software. Here's what I've published so far:

Outside of Code

When I'm not coding, you'll most likely find me strength training — chasing PRs in squats, bench, and deadlifts. It's how I stay disciplined, focused, and balanced.

Daily Drivers & Gear

MacBook Pro 14", Acer Nitro 5, Keychron K4 keyboard, Logitech G305 mouse, Sony WH-1000XM4 headphones.

That's a bit about me. If anything here helps you build better software or think more clearly about engineering, then this page has done its job.

Feel free to reach out — I'm always open to interesting conversations.