/zer0space-terminal.png)
███████╗██╗ ██████╗ ███████╗ ██████╗
██╔════╝██║██╔════╝ ██╔════╝██╔═████╗
███████╗██║██║ ███╗█████╗ ██║██╔██║
╚════██║██║██║ ██║██╔══╝ ████╔╝██║
███████║██║╚██████╔╝███████╗╚██████╔╝
╚══════╝╚═╝ ╚═════╝ ╚══════╝ ╚═════╝
I'm a hobby developer, still early in this and enjoying it that way.
Right now I'm getting properly good at Python instead of just good enough to make something run, and working towards cloud engineering as the direction I actually want to go. Most of what I've learned so far came from building infrastructure I have to keep alive afterwards — which turns out to be an excellent teacher.
name: Siro
location: Switzerland
role: hobby dev, aspiring cloud engineer
learning: Python (deeper) · cloud fundamentals · distributed systems
approach: build it, break it, document what broke| Skill | Level | Where I use it |
|---|---|---|
| Linux / Debian | Daily driver — nine machines to keep honest | |
| Docker / Swarm | Everything I run is containerised | |
| Bash / Shell | Glue, automation, backup scripts | |
| Cloudflare | DNS, Tunnel, Access — no open ports anywhere | |
| Git / GitOps | Repo is the source of truth, no 2am hotfixes | |
| Python | Actively levelling up — main focus right now | |
| PostgreSQL | Backing store for everything stateful | |
| JavaScript | Frontend for the dashboard | |
| Networking | Learning by debugging my own mistakes |
▸ What I'm working on right now
+ Python beyond scripting — structure, testing, actually readable code
+ Cloud fundamentals, working towards cloud engineering
+ Distributed systems: why things break when they're spread out
~ Networking — slowly, mostly by breaking my own setup
~ Databases beyond "it stores things"Things I've internalised the hard way:
| Lesson | What it actually means |
|---|---|
| "Ready" ≠ handling traffic | A green healthcheck is a claim, not a proof |
| Statelessness is a constraint | Retrofitting it costs 10× what designing for it does |
| The dangerous backup | Isn't the one that fails loudly — it's the one that lies |
| Document the unfinished parts | Otherwise you'll rediscover them at the worst moment |
My main playground is zer0space — a self-hosted homelab I run like production: nine Debian machines, Docker Swarm, GitOps-managed, nothing port-forwarded. It's where most of the skills above came from.
📖 docsThe architecture and the reasoning behind it — including what isn't finished yet. |
|
🟢 statusPublic status page. "It's up for me" isn't monitoring. |
/zer0space-pb.png)
