Independent software developer. Low-level by foundation. Modern by practice. Curious by default.
I started on the Commodore 64 — first with BASIC, then 6502 assembly around age 12. When you're writing machine code on hardware that runs at 1MHz, you don't get to be abstract about what's happening. You count cycles. You track register states. You know exactly what the CPU is doing because you told it what to do, opcode by opcode.
That mindset is still here. Understanding the system underneath before building something on top of it is not a preference — it's the only approach that holds up under pressure.
I'm an active member of PRIMAL, a demoscene group creating demos, intros and games for the Commodore 64 and other retro platforms. Group members: BadCode64, CopAss and Nadin.
Notable releases include Wait for 152 Seconds (2024, C64 BASIC demo), Cauldron (2024, 256b intro), Tie vadász (2024, C64 game), Stranger Sins (2023, C64 BASIC demo) and City Grill (C64 BASIC game). In the Transmission64 BASIC demo competition I placed 1st twice and 3rd once. After COVID I started attending Arok Party, got into other retro platforms — Primo, Homelab, Plus/4, Videoton TVC — as a hobby and out of nostalgia.
From the C64 I moved to the Z80, then to PC platforms — DOS, Windows, eventually macOS. Languages accumulated: C, C++, Delphi, Pascal. I built desktop applications, utilities and systems tools, keeping the same close relationship with the hardware and the OS rather than wrapping everything in abstractions.
Web development came naturally. I built my own PHP framework (WebGeneral) from scratch instead of adopting an existing one — not out of stubbornness, but because I wanted to own the code I was shipping. No hidden magic in the routing. No mystery in the ORM. Just code I can read, debug and modify without reading someone else's documentation first.
More recently: AI integrations. I've connected OpenAI, Claude, and Gemini APIs into real production systems — not prototype demos, but live tools doing actual work. Prompt engineering, model selection, cost management, fallback logic. The same precision applies.
The name is a contradiction on purpose. "64" is the C64 — the machine that started everything. "BadCode" is a nod to the fact that all code is imperfect, that shipping something real is worth more than endless perfectionism, and that sometimes the constraints of a 64KB machine produced more creative solutions than unlimited memory ever could.
It's not a humble apology for quality. It's an honest acknowledgment that programming is about trade-offs, not perfection, and that knowing where you started makes it much clearer where you're going.
I work best on problems that have actual technical depth — custom backend systems, tool development, AI-integrated workflows, specialized applications. I'm not a good fit for "build me a WordPress theme" or "set up a Shopify store".
I'm a good fit for problems like this: "we have a complex problem, it doesn't fit an off-the-shelf solution, and we need someone who will understand it all the way down."