David Friedrich

Hi, I’m David.

Full-Stack Engineer & Creative Coder, based in Berlin.

I came to code through art school: I like working out systems and making things work together, and I never lost the creative process on the way. An agency took me from developer to leadership, which made teams and budgets my problem too. Now I take projects whole, so the person deciding your architecture is the one answering your email.

durchnull is German for “by zero” — as in divided by zero: an error in code, a limit that runs off to infinity in math. The curve behind this page is y = 1/x, and the name keeps both readings.

How I got here

Trajectory

Art school meant digital media and visual communication, closer to code than it sounds: real-time installations, generative graphics, machines on microcontrollers (the archive is intact). What stayed is a habit rather than a style: I don’t split design from implementation. How something looks and how it is built are one decision, and an interface that keeps fighting you is usually a data model that went wrong two layers down.

  1. frontend

    Software meets people

    I started with interfaces: JavaScript, CSS and the patience to get a layout right in every browser.

  2. full-stack

    Following the data

    The interesting problems kept sitting behind the interface, so I followed them into PHP and Laravel, and stayed a decade, schema to stylesheet.

  3. agency-lead

    Running the shop

    At Brainspin I grew from developer to project lead to agency leadership: teams, budgets and clients with complicated ideas.

  4. independent

    All of it, end to end

    Since 2025 I take on projects directly: architecture, code, design and delivery from one person. What keeps that safe is the work I like best: building the tooling that lets me trust what ships, whether I wrote it, an agent did, or I inherited it.

Dates, team sizes and scale are on the career page.

What I build for myself

Own products

The two products I own end to end, and the deepest write-ups on this site.

Heal Suite

18 healers · MIT · public beta

findings burden /heal:sweep
before
67.6
after
44.6
Severity-weighted, baseline-excluded: 34% lower over the first two sweeps.

Eighteen specialist LLM auditors under a versioned contract, with measured precision: my answer to code that agents write faster than anyone reviews.

Read the case study

Macrop

macrop.de · TypeScript · live

macro values every read
stored
none
derived
kcal protein carbs fat
One pure engine: the server’s authority, the browser’s preview.

A nutrition planner in full-stack TypeScript where no macro value is ever stored: every number is derived, so the math can’t drift.

Read the case study

Enough about me

Contact

Tell me what you’re building. A rough idea is enough, no polished brief needed. I start from optimism: most things can be made to work.

What are you building?

Contact

A few lines are plenty. These three are what let me give you a straight answer instead of a follow-up questionnaire:

  1. What you are building. The product and roughly where it is: an idea, a codebase someone left behind, something live and struggling.
  2. What is in the way. The part that made you open a contact form. That is usually the whole brief.
  3. When it matters. A date, a launch, a funding round: anything that tells me whether I have the capacity.
Rather write it yourself? [email protected]

What is this about?

0/1000

Goes straight to my inbox, used only to reply (privacy policy). No list, no CRM.