About README
tech, developers, and the code underneath
README is a newsletter about software and the people who write it.
It covers what actually lands in a developer's week: language and runtime releases, the tools that got faster or finally shipped, the platform decisions that quietly change how everyone builds, the licensing fights, the outages, the benchmarks worth believing, and the ones that aren't. Plus longer pieces on the craft itself, because the news cycle is not the same thing as the work.
The format is deliberately plain. Gray background, monospace headings, a single column of text. No autoplaying anything, no cookie banner, no newsletter modal sliding up from the bottom of your screen four seconds after you arrive. It should feel like reading a good README: dense, honest, and skimmable.
who runs it#
README is written and run by Dom the Developer — a professional application developer and software engineer based in Metro Detroit, Michigan. He builds across the stack and the platform matrix: Android, iOS, macOS, Windows, web, Node.js, and Go, with side excursions into VR and AR when the hardware is interesting enough to justify it.
His hackathon work runs from emotion recognition to cloud-based healthcare communication tooling, which is a reasonable summary of the beat here too: systems that touch real people, evaluated on whether they hold up.
- web — domthedeveloper.com
- code — github.com/DomTheDeveloper
- projects — devpost.com/DomTheDeveloper
what you can expect#
- News, not press releases. If a vendor announcement is mostly marketing, that gets said out loud.
- Numbers where numbers exist. Benchmarks get methodology notes or they don't get cited.
- Working code. Snippets here are meant to be pasted and run, not admired.
- Corrections in public. Mistakes get fixed in place with a note, never quietly rewritten.
how it's built#
This site is a few hundred lines of Python that turn structured content into static HTML, plus one stylesheet and one small script. There is no framework, no build server, no client-side router, and no hydration step. It deploys as flat files. Pages are typically under 30 KB and there is no third-party JavaScript on any of them.
The full colophon has the details.
archive notes#
The archive runs back through 2025. Pieces are dated to the window they cover, so reading a year top-to-bottom gives you that year in order. Individual posts are stable at their URL — nothing here gets renamed or deleted.
get in touch#
Tips, corrections, and arguments are all welcome. Corrections get priority. Reach out through domthedeveloper.com.