I am a systems builder. I work across software, automation, product questions, and operations, following the problem rather than forcing it into a familiar stack.
Frameworks matter, but they are not the starting point. I begin with the users, constraints, data flows, failure modes, and feedback loops that define a useful system. That perspective makes it easier to cross boundaries when the work asks for it: architecture, implementation, deployment, and the operational details that follow.
Autonomous tools can remove repeated work and widen the range of what one builder can deliver. I use them as leverage, not as a substitute for judgment. Architecture, tradeoffs, verification, and accountability stay inside the process.
I am most interested in products with a real problem underneath them: work where careful engineering changes the quality of the outcome.
Public work that can be inspected.
My public work includes Python, DevOps, automation, open-source maintenance, and years of technical questions and answers. SpotifyScraper, a Python library for extracting Spotify data without official API authentication, is one visible example. It is not a complete map, but it is an honest one.
Foundation
Python and systems work
Building software and automation tools while paying attention to the operational details that keep them useful after release.
Public loop
Learning in the open
Open-source maintenance and technical answers create a visible loop: build, document, answer questions, and improve the result.
Current
End-to-end systems work
Working across product questions, software implementation, automation, and operations while keeping verification inside the process.
