Backend Developer

Phil Eaton Portfolio

Personal site of a database-internals engineer (ex-Oracle, ex-EnterpriseDB, TigerBeetle co-founder) who writes from-scratch implementations of databases, garbage collectors, and consensus protocols, and runs a 3,000+ member book club on systems programming.

Database InternalsDistributed SystemsGoConsensus Protocols

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Build-it-yourself posts instead of explainer posts

Rather than summarizing how Raft or a write-ahead log works, his posts walk through building a minimal working version from scratch, with the code alongside the explanation — a format that proves understanding rather than just describing it.

2

Community infrastructure attached to the writing

A companion subreddit, Discord and book club turn a solo blog into a hub other systems programmers gravitate to, which compounds the credibility of the writing itself.

3

A narrow, consistent topic focus

Nearly every post touches databases, garbage collection, or distributed consensus. That focus makes the site legible as "the databases person" rather than a general tech blog, which is exactly the reputation that leads to database-engineering job offers.

What Backend Developers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Pick one narrow technical area and let most of your posts orbit it — a focused site builds a reputation faster than a broad one.

  • Show a minimal working implementation of the concept you're explaining, not just a description of how it works.

  • If your writing attracts a community, give it a place to gather (a subreddit, Discord, or book club) instead of leaving it scattered across comment sections.

Ready to build your portfolio?

Follow the Backend Developer roadmap — skills, projects, and timeline to get hired.

Backend Developer Roadmap