ABOUT_

An engineering publication that shows its work.

Bodan the Backend turns technical experience into clear, verifiable analysis for people who build systems.

Good technical content does not repeat documentation: it adds context, measures consequences and explains why a decision works in a specific situation.

01 / MISSION

Make the reasoning behind software visible

Architecture decisions are rarely universal. They depend on the team, load, budget and product stage. We document those constraints before presenting a solution.

The goal is not to publish more. It is to build a small library of references worth returning to.

02 / PRINCIPLES

Editorial principles

01

Evidence over authority

We distinguish sources, first-party measurements and editorial inference.

02

Context over recipes

We explain when to use a technique and when to avoid it.

03

Clarity over complexity

Precision does not require inaccessible writing.

04

Revision over speed

Articles are updated when data or platforms change.

03 / PROCESS

From experiment to article

  1. 01
    Form a question

    It must be specific and allow a result that contradicts intuition.

  2. 02
    Build a test

    When the Lab opens, each test will publish its environment and parameters.

  3. 03
    Interpret limits

    We separate measurements from inference and declare biases.

  4. 04
    Publish and correct

    The analysis links its sources and stays open to review.

AI may assist with finding sources, comparing candidates or preparing drafts. Selection, verification, editing and final publication remain under human review.

04 / STACK

Technologies that appear often

GoPythonPostgreSQLDockerGoogle CloudMicrosoft AzureOpenTelemetryTerraform

05 / AUTHOR

Ariel Bodan — Backend Engineer

I design APIs, backend services and data systems with Python, Go and PostgreSQL. Bodan the Backend is where I document how I make architecture, performance and cloud decisions.

NEXT_

Start with an analysis or browse the news.

Explore articlesNews