Every personal website is a promise to the future. This one is mine: a quiet corner of the internet where I document what I'm learning, what I'm building, what I'm reading, and what I can't stop thinking about. No algorithm, no engagement metrics, no hot takes written to expire in a week — just notes, set in warm ink, that I'll be able to reread in five years without cringing (too much).
My name is Nirmit, and this is The Boring Edit.
What lives here
The site is organised around a few recurring kinds of writing:
- Articles — proper write-ups on code, systems and things I've gone deep on. The technical meat of this site.
- Journey — a running log of where I am: what I'm working on, what I'm stuck on, and what changed since the last entry. Honest, not curated.
- Roadmaps — the plans themselves. Numbered series that unfold part by part, so you can follow along — or catch up later, in order.
- Resources — the books, articles, tools and links worth keeping. If it's on this site, it earned its place.
- Philosophy — the why behind the what. Opinions about building, learning and living with software, held loosely enough to be corrected.
- Interesting things — the loose ends: a demo, a quote, a chart, a bug that taught me something. The stuff that doesn't fit a category but deserves to exist somewhere.
None of these require perfection. This is a notebook, not a newspaper.
Why "boring"
The name is deliberate. Boring is what happens when a thing is understood, reliable, and calm — and those are exactly the qualities I want in the software I build and the words I write. The most durable technology is boring. The best writing doesn't shout. A boring edit is the version of a paragraph you reach after cutting everything that was only there to impress.
The flashiest thing on this page is a single loud orange. Everything else is paper, ink, and hairlines.
So this site will stay deliberately small: fast static pages, a dot grid for texture, no trackers, no pop-ups, no newsletter pop-over asking for your soul. Just RSS if you want to follow along the old-fashioned way.
How this will work
The writing here is plain markdown files on my machine. A small build step compiles them into this site — math typeset, code highlighted, every page prerendered to static HTML. When I write something new, the host simply gets new pages added to it. There's no CMS behind this, no database, no server quietly billing me by the hour.
A few commitments to make this worth visiting:
- Series over scattered posts. Bigger topics — a language, a system, a deep skill — will run as tracks: numbered parts you can binge from part 01, regardless of when each part was written.
- Learn in public. Half-finished understanding is welcome here, clearly labelled as such. Corrections are welcome even more.
- Write for the reread. Every post should still make sense in a year — to you, and to future me.
The philosophy, stated once up front
If the site has a constitution, it's these three lines:
- Slow is smooth. Depth beats frequency. I'd rather ship one post that still matters in a year than thirty that don't survive the week.
- Own the Means. The words live in markdown files I control, compiled to pages I host, on a domain I own. If a platform dies, nothing here dies with it.
- Show the work. Roadmaps include the wrong turns. Resources include the ones I abandoned and why. A journey log with only wins is a highlight reel, not a journey.
Where to start
- If you want the ongoing story, the Journey entries will accumulate here over time — this post is entry zero.
- Big topics will appear as Tracks on the tracks page, each part numbered so you can pick up exactly where you left off — the site even remembers what you've read, locally, in your own browser.
- The shelf will grow as resources earn their place.
That's the tour. First real entries are on the way — see you at part one.