---

title: "Launching The Late Night Project" date: "2025-01-15" description: "Why I decided to build in public, what I'm shipping, and how this site came to be." tags: ["meta", "intro", "next.js", "tailwind"]

Launching The Late Night Project

It's 11:47 PM. My third cup of coffee is getting cold on the desk. The code editor is open. A blank page is staring back at me.

This is where most of my best work happens.

Why Build in Public?

I've been shipping software professionally for years — mostly in the shadows of corporate projects that never saw the light of day. Great work that got buried in internal tools, deprecated products, and NDA agreements. That ends now.

The Late Night Project is my attempt to change that pattern. It's a solo software studio where I build things I actually care about, and I document every step of the way.

The Stack I'm Starting With

I spent longer than I'd like to admit picking the tech stack. Here's what I landed on and why:

Next.js 16 with App Router — The App Router is finally mature enough to build on confidently. RSCs (React Server Components) make it easy to keep things fast without shipping unnecessary JavaScript.

Tailwind CSS v4 — The new PostCSS-based architecture is cleaner. No more tailwind.config.js sprawl. Just import and go.

TypeScript, obviously — I've been burned too many times by runtime type errors. Everything is typed now.

What's Coming

The build log is the first major feature. After that:

• A projects page showcasing what I'm shipping
• A newsletter for people who want updates without the social media noise
• Eventually, some experiments — small tools and toys that might become something bigger

On the Name

"The Late Night Project" isn't just aesthetic branding. It's accurate. This work happens after the day job quiets down, when the notifications stop, and I can actually think.

Late nights are underrated. The world goes quiet and ideas get loud.

More soon.