Technical Debt Mitigator
I help organizations mitigate technical debt in business-critical legacy systems — reducing technical risk, extending system lifetime, and enabling modernization without unnecessary rewrites.
Technical Debt Mitigation→ Legacy Systems→ Architecture→ Delphi→ .NET Modernization
35+ years of software engineering experience. I've been programming since 1990, and in that time I've learned one thing that still holds true: a system's lifespan is decided in the design, not in the code. I build systems that run for decades — because the knowledge lives in them once, in one place.
years at the keyboard
From BASIC on an eight-bit Atari to multi-LLM pipelines — one continuous thread
years in production
The d.process platform, deployed in 2010, still runs in public administration today
languages and VMs of my own
From a bytecode interpreter in 1997 to today's Atra language — designing languages is a craft you can't fake
Story
My first lines of BASIC on an eight-bit computer. This is where a habit started that I never shook: before writing the first command, I want to know what the whole thing will look like.
Control and Measurement — digitizing sensor data. My first encounter with a theme that still follows me today: how to get data from the physical world into a system in a form you can actually work with.
A control system for a school robot in Borland Pascal — over 6,200 lines, a custom bytecode and virtual machine. Instead of hard-wired movements, the robot got a language it could be programmed in. 1st place in the regional round of the Czech national student science competition (SOČ). First proof that separating "what" from "how" pays off. Source code on GitHub →
An Ing. degree in computer engineering from the Faculty of Electrical Engineering at the Czech Technical University in Prague. A formal foundation under an intuition that had until then come purely from practice.
I built a development department from scratch and designed the d.process platform: a metadata-driven system with its own d.script scripting language, a virtual machine, and federated queries across SQL, LDAP and files — at a time when the term low-code didn't even exist yet. In production since 2010; still running in public administration today.
A standalone project outside d.process: a web-based repository for documents undergoing authorized conversion. It replaced physically carrying files around on media — the same principle that, a year later, gave rise to d.process: make a process digital where it used to mean paper or a disk in someone's hand.
Independent practice: the Atra language and Atrust platform as a new generation of the same idea, IT Construction Oversight for software clients, and AI-pipeline designs where language models are a first-class — and replaceable — part of the architecture.
Philosophy
Every system I've ever designed — from the 1997 robot to today's AI pipelines — rests on the same principle: knowledge lives in the system once, in the data model and contracts, and everything else is derived from it. The screen, the report, the API and the AI agent are just different projections of the same model. When a rule changes, it changes in one place — and propagates everywhere on its own.
A bad system can be predicted before it's even built — from the conditions it's built under. My job is to change those conditions in time, not fix the consequences later.
Permissions belong in the data model, not on the screens. Every consumer of the system — web, desktop, and an AI agent alike — then gets the correct restrictions automatically, with no exceptions.
A system isn't judged by what it looks like in month one, but by what the thousandth change costs. My track record is measured in years of continuous operation.
What I'm working on
How I work
Architecture is assessed against the repository, the model and the documentation, not in a meeting room. I work remotely for clients anywhere — the same availability for Prague or Ostrava, no travel expenses, no waiting for a site visit slot.
Collaboration runs on a framework agreement with an agreed scope: I design, assess and watch the load-bearing walls of the system. The decision always sits with the client — I have a duty to warn, not a right of veto.
I am a registered provider of alternative performance (náhradní plnění) under § 81 of Act No. 435/2004 Coll. For companies with more than 25 employees, that means the same money that would otherwise go to the state can pay for independent architectural expertise. How it works →
Atriplex Algorithmics isn't backed by any vendor or platform. When I assess someone else's design, I represent one interest only — the client's. Audit recommendations aren't tied to what I develop myself, and the deliverable is a written report the company keeps using regardless of who performed the audit.
Contact
Write me a few lines about your project or system. The first consultation is free of charge and takes place online — I'll tell you straight where the load-bearing wall is and where it's just plaster.
jakub@lebeda.eu →Ing. Jakub Lebeda · Atriplex Algorithmics · Company ID (IČO) 19074671 · +420 607 720 317 · Provodín, Czech Republic