This blog is where I will keep the engineering notes that are useful after the current sprint is over.

I write Rust, build backend systems, and keep notes while the details are still sharp. The goal is simple: document the code, tradeoffs, debugging paths, and mistakes that are worth remembering.

Most posts will be one of three things:

  • Deep dives into Rust and backend behavior.
  • Build journals from projects like the Async Job Queue.
  • Career notes that are specific enough to be useful later.

Here is the shape I want from a post:

en 
use std::time::Duration;

struct Job {
    id: u64,
    timeout: Duration,
}

impl Job {
    fn should_retry(&self, attempts: u8) -> bool {
        attempts < 3 && self.timeout.as_secs() > 0
    }
}

The code should be small enough to inspect and real enough to matter.

A dark terminal workspace with Rust code and build logs
The starting point: small notes, working code, and a static site that stays out of the way.

I am starting with a static blog because the workflow should stay boring. Markdown in Git. Zola for builds. Railway for deploys. No database, no login, no admin surface.

If a note helps me rebuild context faster, it belongs here. If it only sounds impressive, it does not.