01 / INTRO
A working atlas of one engineer's notes, decisions, and systems.
I'm Petros — software engineer in Athens. This site is a small index of the work I keep returning to: how systems are shaped, what they cost, and why the second-best decision often wins. It isn't a portfolio. It's a sheet you can fold up and take with you.
02 / NOW
Current bearings.
- Focus
- Distributed systems, observability, and the small craft of API design.
- Reading
- Naur, Chiang, Christopher Alexander — slowly, twice.
- Tooling
- Go, TypeScript, Postgres, Linear, plain text, paper.
- Open to
- Conversations about platform teams, evals, and patient codebases.
03 / FIELD NOTES
How the work usually moves.
A diagram is not a map. It's a contract between intent and what actually shipped. The version below is the one I keep redrawing.
- A Observe Talk, watch, instrument.
- B Sketch Pencil, then prose.
- C Spike Smallest cut that proves it.
- D Decide Write the trade-off down.
- E Ship Boring on the outside.
- F Revisit In a quarter, mercilessly.
04 / MAP OF WORK
A short atlas of projects.
Names withheld where appropriate. Tradeoffs over outcomes.
-
REC · Platform · 2024–25
Quiet observability
Replaced a noisy dashboard culture with three durable signals and a runbook. Pages dropped 64%.
-
REC · API · 2023
Boring contracts
A versioning policy nobody complained about. The clearest writing was the most contested PR.
-
REC · Internal · 2022
Eval harness
A tiny test rig that made an opinionated team agree on what "better" meant for two months.
-
DRAFT · Open · 2026
Field notebook for engineers
The reason this site exists. Notes, decisions, and the small loops worth keeping.
05 / INDEX OF WRITING
Selected notes.
- 2026·04·19 On second-best decisions 7m
- 2026·03·02 Three signals are enough 5m
- 2025·11·14 Why I keep redrawing the same diagram 9m
- 2025·08·30 A week on the wrong abstraction 6m
06 / CHANNELS
Open channels.
- Email hello@stergioulas.com
- Profile linkedin.com/in/petrostergioulas
- Source github.com (soon)