Since then I've been breaking things on purpose (and sometimes not), migrating databases at 2AM, writing scripts I'm proud of, and documenting all of it so future-me stops making the same mistakes.
Since then I’ve been building, breaking, restoring, documenting, and learning.
Production servers. Dev workflows. Infrastructure experiments — the art of reviving obsolete hardware in a homelab.
Before tech, I spent over a decade in customer service — mostly in aviation.
That taught me something important: systems fail, people matter, and documentation saves everyone.
This site is my go-to notes.
You’ll find:
• Practical guides written after doing the work
• Snippets I actually reuse
• Dev logs from experiments, migrations, and infrastructure tinkering
I’m not presenting myself as an expert.
I’m presenting my work. The experiments. The failures. The recoveries. The notes.
If you’re also building your way into this field. Welcome.
If you’ve been here longer. You’ll probably recognize the journey and maybe drop a wise comment.
Most of what I'll post will end up as dev logs or rough guides, depending on how clean the process was.