A house on the internet

Somebody is always home.

A machine in Virginia that has been thinking about prime numbers since July, a library of engineering post-mortems and Bengali short stories, and a workshop of tools you can pick up and use. Wander in.

Bitan SarkarKolkata, India
~/bitan — livelive
$ whoami bitan-sarkar
$ stack Java · Spring WebFlux · AWS
your address
resolving…
your speed
a few MB, about five seconds
this box never sleeps

Computing right now, and has been for months

The Lab

Where I write things down

Engineering deep-dives and post-mortems from real builds, and short fiction. Different muscles, same notebook.

All 16 posts

Under the hood

This site is the case study

No WordPress, no Contentful, no database. A custom CMS, a devtools platform and an always-on compute engine, in one Node process on one small box.

databases
0
Node process
1
JSON files hold it all
7
CMS licence
$0

Everything you are reading — the copy, the projects, the posts, the timeline — is served from flat JSON and Markdown that I edit through an admin panel I wrote. Saving a post writes atomically to disk, revalidates only the routes that data renders, and pings IndexNow so the crawlers come back.

The interesting part is not that it works. It is which trade-offs it makes, and where they stop being the right ones.

  1. client

    Browser

    • SSR first paint
    • no data fetch on load
  2. HTTPS

    edge

    nginx

    • TLS
    • security headers
    • alias /uploads/
  3. proxy_pass → 127.0.0.1:3002

    gate

    Middleware

    • per-IP + global budget
    • jose HS256
    • static assets excluded
  4. NextResponse.next()

    app

    Next.js standalone · pm2 · one fork

    (site)

    /admin

    /api

    engine

    sandbox

    • server actions
    • revalidatePath
    • instrumentation hook
    • one run at a time
  5. fs read / atomic write

    data

    DATA_DIR

    content.json

    projects · skills · timeline

    posts.json + posts/*.md

    engagement.json

    • tmp + rename()
    • survives deploys
    • git-diffable

Let's talk

Open to opportunities.

I'm selectively exploring senior engineering roles at product-first companies. If you're building something interesting, let's talk.