Most of my work starts with a simple question: what can we remove so the system becomes faster, safer, and easier to run? I like building things that hold up outside a demo.

"Disziplin formt Systeme, Systeme formen Erfolg."
"Discipline builds systems, and systems create success."
— Sj
I spend a lot of time inside Linux terminals, network maps, and half-finished notebooks. I like figuring out why systems break, then rebuilding them in a way that feels cleaner and easier to maintain.
My projects usually mix software with real constraints: unstable inputs, noisy logs, devices that are not always cooperative, and timelines that move fast. That is the part I enjoy most.
I have worked with Kali Linux, networking fundamentals, automation scripts, and Arduino-based prototypes. Lately I have been going deeper into ethical security testing and operational tooling.
I am still learning every week, and that is intentional. I would rather ship honest, useful work than polish an idea forever.
A mix of tools I rely on daily, plus areas I am currently sharpening through project work.
These are projects I actually built and iterated on, not polished concept pieces.
Role: System Design + Development
Tech:
Features: Automated scanning with structured output parsing
Focus: Modular command flow and reusable scan profiles
Outcome: Cut analysis time when validating known targets
Role: Automation Builder
Tech:
Features: Task scheduling with repeatable workflow chains
Outcome: Removed repetitive manual steps from daily ops
Role: Embedded Developer
Tech:
Features: Soil-moisture driven automation loop
Outcome: More stable watering with less waste
Role: System Designer
Tech:
Features: Object tracking paired with motor control
Outcome: Working prototype used for field tests
Role: Full-stack Developer
Tech:
Features: Custom UI and ordering flow
Outcome: Stable MVP ready for growth
If a system cannot be split and reused, it becomes expensive fast.
I prefer safe defaults over “fix it later” security patches.
Useful and shipped beats perfect and unfinished.
Small releases, fast tests, and honest postmortems.