I hold a Master's degree in Electronic Engineering, with a focus on industrial control systems and PLCs — so before I was writing Python at midnight, I was elbow-deep in ladder logic and control loops.

Professionally, my main field is Embedded Systems. Software development has mostly been something I did for fun on the side — late-night projects built to scratch my own itch rather than ship to a market. I've now decided to open source that work, mainly because I want real feedback to make these projects genuinely better, not just personally satisfying.

So consider this less "here's my portfolio" and more "here's what I've been quietly building — tell me what's wrong with it."

📍 Somewhere between a PLC rack and a terminal 🎓 M.Sc. Electronic Engineering — Industrial Control Systems & PLCs 🔧 Professional focus: Embedded Systems 💻 Software development: a very serious hobby

It started with an ATmega chip, a breadboard, and more magic smoke than I'd like to admit to. From there it was a short, inevitable slide into designing my own PCBs — because at some point "just wire it by hand" stops being charming and starts being a fire hazard.

PCBs led to robotics, because once you can design the board, you start wondering what happens if you bolt motors to it. Robotics led to Arduino, because sometimes you just want the thing to blink without re-deriving your own bootloader first. Arduino led properly into embedded systems, where I started actually understanding what I'd been doing by accident for years.

Eventually that turned professional and industrial: PLCs and control systems — the kind of environment where a bug doesn't crash an app, it stops a production line, and everyone in the building finds out at the same time.

Somewhere in the middle of all of it, I kept building little PC programs on the side — not for anyone else, just because I needed a tool that didn't exist yet and refused to wait for someone else to build it. That habit never really stopped. It just eventually got a GitHub account.

Currently: still doing that.

What's already evident from the repos:

• Built and shipped 17+ standalone desktop applications end-to-end — design, backend logic, packaging, and documentation
• Deep, hands-on comfort with Modbus/RS-485 industrial protocols, PLC logic analysis, and OT security concerns
• Consistent focus on security-conscious engineering — encryption, hardened defaults, no telemetry, no silent data collection
• Comfortable working solo across the full stack of a desktop product: UI, systems programming, packaging, and end-user docs

• 🥔 I have a signature documentation format called the Potato Protocol — if you can microwave a potato, you can run my software. No exceptions granted.
• 🌙 A suspicious number of my commits happen after midnight. Coincidence? The commit timestamps say no.
• ☕ My IDE has, at various points, contained more coffee-ring stains than actual bugs.
• 🐛 I've debugged a race condition by staring at it long enough that it got embarrassed and fixed itself. (This is not a repeatable methodology.)
• ⚡ I've spent more hours reading PLC ladder logic than most people spend watching TV in a year.
• 🦊 My mascot is a cyber-fox because regular foxes don't ship single-file executables.

I'm always up for teaming up on desktop tooling, industrial/OT software, embedded systems, Raspberry Pi projects, or anything privacy-first. If you've got an idea, a gap you've noticed in the tooling world, or just want to build something that doesn't need a cloud subscription to function — open an issue, send a message, or just say hi.

If one of these tools saved you an afternoon (or a server), you're welcome to buy me a coffee — entirely optional, always appreciated, never expected.