Writing to be read
Practical tips for writing clear, readable technical documentation and notes, focusing on structure, formatting, and user psychology.
Phil Eaton is a staff engineer working on Postgres and software internals, sharing insights on databases, systems engineering, and life deep in the software stack.
169 articles from this blog
Practical tips for writing clear, readable technical documentation and notes, focusing on structure, formatting, and user psychology.
A guide to writing a simple JSON parser, covering lexical and syntactic analysis, with a practical implementation example.
A developer shares their experience using FreeBSD CURRENT as a daily driver for software development, detailing the setup, workflow, and hardware issues that led them to switch back to Arch Linux.
A review of Paul Graham's 'ANSI Common Lisp' book, comparing it to other Lisp resources and praising its clarity and conciseness.
A guide to setting up a minimal Common Lisp project using ASDF and Quicklisp, including creating packages and systems.
An interview about BSDScheme, a Scheme interpreter, and the developer's experience switching from C to the D programming language for its features.
A developer shares challenges and solutions from building a Scheme interpreter in D, covering data representation, function evaluation, and AST design.
A guide to automating FreeBSD deployment on Linode using custom disk images and a Python script, bypassing manual installation.
A technical tutorial on building a basic web service using the Racket programming language, exploring its web server libraries and syntax.