BoringDocs: Engineering Documentation Without the Fluff
Most engineering documentation is written to impress, not to help — padded introductions, marketing language, and concepts explained before you know why they matter. BoringDocs skips all of that. Every article starts from a real problem, works through it with actual code, and stops the moment the problem is solved.
What's Here
Topics are grouped by concern, not by technology, so you can go straight to the area you're working in — from terminal basics to shipping production AI agents.
Foundations
Core skills that underpin everything else.
- Terminal & Command Line — essential commands, shebangs, and cross-platform script execution
- Node.js Fundamentals — runtime model, npm/npx, package types, async I/O, and EventEmitter
- Data Representation in Computing — number systems, signed integers, character encoding, and Base64
- Buffers & Streams — ArrayBuffer, TypedArrays, Node.js Buffers, streams, piping, and backpressure
Backend Development
Building services and the data layer behind them.
- Relational Databases & SQL — schema design, SELECT, aggregations, joins, and safe writes
- REST API Design & Specification — resource modeling, HTTP verbs, versioning, OpenAPI, authentication, and common mistakes
- NestJS — framework overview, controllers, providers, and project structure
Async & Messaging
Decoupling work and handling it reliably.
- Message Queues & RabbitMQ — why queues exist, AMQP, RabbitMQ exchanges, bindings, and broker internals
- Inngest & Event-Driven Workflows — durable functions, steps, retries, fan-out, scheduled jobs, and local development
Infrastructure & Tooling
Shipping and organizing your work.
- CI/CD & Deployment — GitHub Actions, VPS setup, Nginx, SSL, and domain configuration
- Nx Workspace & Monorepos — monorepo vs polyrepo tradeoffs, Nx setup, and app/library structure
AI & Agent Development
Building agents that actually ship, not just demo well.
- Building Agents with LangChain — a 15-article series from your first prompted agent through tool calling, memory, RAG, multi-agent systems, human-in-the-loop, and a production-ready capstone
The Approach
Good documentation has one job: get you from problem to solution. That means:
- Start from the problem, not the technology
- Show working code, not idealized pseudocode
- Cover what you'll actually encounter, not every edge case
- Stop when the topic is done — no padding, no upsell to the next section
What you won't find here: marketing language, version numbers that will rot, or concepts explained before the problem that motivates them.
About the Creator
Created by Bappi Rahman, a software engineer based on the conviction that documentation is a tool, not a showcase.
- GitHub: @bappirahman
- Twitter: @_bappi_rahman
- LinkedIn: Bappi Rahman
- Email: cs.bappirahman@gmail.com