Most developers learn how to make software work. I also learn how it fails, from the web layer down to the assembly.
That mindset shapes everything I ship: fast, clean, and hard to break.
I don't slap a framework on top and hope for the best — I understand what happens underneath, from how memory is laid out to how a network packet gets parsed. That's why my tools tend to be small, direct, and reliable instead of bloated.
An 8-channel, Ethernet-controlled relay controller — real hardware, not a prototype.
Web panel, physical buttons, schedules, scenes and a secured REST API, built on an ESP32-S3,
designed to run 24/7 and recover from faults on its own.
Sold assembled and cased at pixelshop24.com — firmware updates and documentation are on GitHub.
| ⚙️ Domain | 🔧 What I work with |
|---|---|
| Embedded & IoT | ESP32, Arduino, Ethernet/W5500, sensors, firmware OTA |
| Backend & Automation | Python, Flask, REST APIs, bots, proxy networking |
| Native & Desktop | C++, C#, Qt |
| Web Front | HTML, CSS, JavaScript |
| Low-Level | Assembly, memory & binary internals |
| Mobile & ADB | Android platform tools, device control, ROM compatibility |
| Security | Secure-by-design development, defensive mindset |
╔═══════════════════════════════════════════════════════════╗
║ ║
║ "If you can't explain what your code does at the ║
║ byte level, you don't really understand it." ║
║ ║
╚═══════════════════════════════════════════════════════════╝
- 🔒 Security first — every feature is designed with the assumption it will be attacked
- ⚡ No bloat — if a dependency isn't earning its keep, it gets cut
- 🎯 CLI over GUI — the terminal is the control room, not a fallback
- 🧪 Break it yourself — if I haven't tried to break it, I don't ship it
