05 / The collection

Résumé-ish.

Capabilities, working style, and places to see the evidence. Dates and employers can remain in the conventional version.

I am most useful when something technical is important, confusing, repetitive, or quietly on fire.

What I do

Systems & networking

Design, operate, segment, troubleshoot, and document infrastructure with an emphasis on understandable boundaries and dependable behavior.

Automation & small software

Turn repeated manual processes into modest, maintainable tools—without automating away the judgment the process still needs.

Troubleshooting

Separate symptoms from causes, test assumptions, narrow the search space, and leave behind a better diagnostic path for next time.

Documentation

Create diagrams, procedures, notes, and explanations that reduce dependence on memory and make ownership transferable.

How I work

Prefer evidence to ceremony

Working systems, concise notes, tested fixes, and visible outcomes are more persuasive than a page full of adjectives.

Build for the next person

Names, diagrams, defaults, failure messages, and operating notes should help someone who was not present when the system was created.

Keep the weirdness useful

Curiosity and side projects are assets when they sharpen judgment, create reusable tools, or reveal a better way to frame the problem.

Next step

Replace generalities with proof

This page is intentionally honest scaffolding. As real projects and notes are added, link each capability to a specific example and let the collection become the résumé.