Systems
How machines, networks and workflows actually behave.
About
I am curious to a probably inconvenient degree. If something catches my interest, there is a real chance I am still researching it several hours later.
I like problems that make me stop and think. The fun part is usually not already knowing the answer, but figuring out why something works the way it does.
A lot of my projects start with a small thought: why does this not exist, or why is this more annoying than it needs to be? Sometimes the result solves a meaningful problem. Sometimes it saves ten seconds.
10 seconds saved
Every 10 seconds counts.
Sometimes the automation takes longer than the original problem. That is not the point.
My technical background started in system administration, and I currently work in IT support. That mix has shaped how I approach problems: investigate carefully, understand the system, then improve the workflow.
Interests
How machines, networks and workflows actually behave.
Turning rough ideas into usable tools.
Local models, assistants and practical automation.
Following clues until the thing finally makes sense.
Easy to start. Occasionally difficult to stop.
Regular training, useful reset button.
A good way to leave the chair.
Doing things that are not debugging.
I do not have the entire roadmap figured out, and I am fine with that. For now I want to keep getting better technically, get closer to systems again, keep building software, and see whether development becomes a larger part of the path.
Curious what all that turns into?