Open Source

I publish the code behind the things I build.

The finished interface is only one part of a project. I keep the source, release history, and technical notes public so the decisions can be understood, the changes can be followed, and useful parts can be reused.

Source codeChange historyWorking releases

Open enough to be useful.

A public project should be understandable, not simply downloadable.

  1. 01

    Show how it works

    The structure and technical choices remain visible beyond the final interface.

  2. 02

    Keep changes visible

    Commits, releases, and issues give each project an honest history.

  3. 03

    Make reuse practical

    Others can inspect an idea, adapt what helps, or point out what can improve.

Grouped by what it does.

Products, infrastructure work, and ongoing experiments each have a different purpose, so I keep that distinction clear.

Products

Windows tools I maintain for practical support and diagnostics.

03 repositories

Engineering

Network designs, topology files, configuration, and infrastructure automation.

04 repositories

Collaborative & experiments

Team work and smaller ideas that I continue to explore in code.

03 projects

Everything starts with the repository.

Browse the source, current releases, open issues, and the work still in progress.

Open my GitHub