Muneer Alam Writing

Notes from the build.

How something works. Why a decision mattered. What happened when the first version met reality. Published articles and notes, here and on DEV.

01

5 October 2026 · 4 min read · DEV

Three yeses, two living rooms, and one missing question

A scrapbook for a group-planning conversation: separate what the messages actually say from what is still unresolved, then ask one useful next question. My development notes follow the Gemma-backed prototype and its grounded quotation checks.

Original publication dates are preserved. External articles retain their original links; project case studies here reflect the reviewed implementation.

Subscribe via RSS ↗

Inside the projects

The work has a longer story.

A keyboard that sounded late. A research draft that needed a history. A puzzle generator that became a game. Read the engineering and the experiences behind the project cards.

01

safedump · 3 min read

The traceback ends. The questions don’t. ↗

A Python exception names the failing line. safedump keeps the runtime context that helps explain it: bounded variable snapshots, exception chains and thread state, saved locally for inspection after the process stops.

02

Klicky · 3 min read

The code was fast. The keys still sounded late. ↗

Klicky turns physical keyboard events into sound. My Linux work follows the entire path from evdev input to cached PCM and the audio mixer, where a small software timing number can hide a much larger buffer delay.

04

ReGit · 3 min read

A finding should have a history you can follow. ↗

ReGit separates a research team’s live draft from the version worth citing. Immutable source files, collaborative editing, explicit commits and prose merges keep the path from a claim back to its evidence visible.

05

RhinoBox · 4 min read

One upload. Two very different storage decisions. ↗

RhinoBox combines a file workspace with a Go service that inspects JSON structure and recommends SQL or document storage. Its most revealing details are the boundaries between a recommendation, a database write and a downloadable archive.

06

codelines · 2 min read

A small map of an unfamiliar codebase. ↗

codelines counts physical lines across a repository, groups the result by extension and directory, and exports complete JSON or CSV. The interesting work is deciding which files belong and keeping the answer consistent across every output.

07

Ascent · 3 min read

When an event depends on the software. ↗

Ascent connected participant and staff workflows across a techfest: registration state, QR entry, submissions, rewards and leaderboards. This story follows my backend and operations work within a larger team-built platform, now preserved as a historical archive.

08

Arch portfolio · 3 min read

The portfolio was also the project. ↗

My previous portfolio turns a browser tab into an Arch-inspired desktop. A terminal, movable windows, virtual files and a Pocket interface offer a different way to explore my work, alongside the current reading-focused site.

09

BOOP · 3 min read

A word list became a book. Then it became a game. ↗

Book Of Organized Puzzles began as a Python word-search book generator. Its web version grew into two experiences: create a printable puzzle book, or stay in the browser and play, with touch, hints and saved progress.