Technical Field Notes
A working notebook on systems engineering — infrastructure, integration, security, and the decisions behind them.
This is not a general developer blog. It is a specific record of the systems I design, the trade-offs I have to make, and the questions that come up when I look back at a project six months later.
Every post is written with the same rule: lead with the problem, not the tool. If a piece of infrastructure exists, it exists because something in the real world required it. The interesting part of systems engineering is not the list of products that were installed. It is the reasoning that determined which list, in which order, and with what constraints.
What you'll find here
Technical
Infrastructure design, backup architecture, virtualization, cloud, security — written from practice.
Reflection
Notes on systems engineering as a discipline, and the career decisions behind it.
Video (future)
Recorded walk-throughs of the architectures described here — same content, different format.
Feedback
No public comments. Send a message directly — corrections, questions, follow-ups all welcome.
Content is written in plain MDX under version control. There is no CMS, no tracking pixels, and no ad network. If a post needs updating, it is edited and re-deployed — like code.
For feedback, corrections, or follow-ups, use the feedback form. For the professional picture — case studies, experience, certifications — my portfolio lives at danny.rw.
Latest post
All posts →
The Veeam Hardened Repository, Configured Properly
A short walk-through of the Linux XFS hardened repository that makes Veeam backups survive ransomware — with the settings that actually matter.