th3chris
About

Christian Daniel

Cloud Solution Architect & AI Engineer with 25+ years of experience.

Who I am

Senior engineer and architect since the early 2000s. Today's toolkit: cloud-native platforms, AI architecture, and step-by-step modernisation of grown systems. The focus: bringing complete software projects to production — solo as full takeover, or integrated into existing teams: as architect, senior engineer, mentor or in an advisory role, depending on what the engagement needs.

I care less about the newest technology than about truly understanding a system and making decisions that still hold up a few years later. Better built once cleanly than patched three times.

Career

I started professionally as a Programming Analyst at a Frankfurt brokerage — securities analysis, stock exchange reporting duties, early internet migration. Then came ticket.international with point-of-sale and vending systems, followed by a move to Luxembourg with Felten S.A., where I built MES systems for biotech and cosmetics production. In 2010 I went independent — because I wanted variety, to go deeper into more topics and build a broad knowledge spectrum, instead of staying in the same narrow slice.

The common thread across the years isn't a technology, it's a stance: understand a system as it actually works, question existing solutions, domesticate new technology rather than just adopting it. Banks, industry, mid-market, enterprise, startups — every engagement taught something that stayed relevant in the next. Above all this: the hardest architecture decisions are rarely technical. They're organisational.

Roots

Where the building drive came from: Atari ST 1987, custom games in GFA Basic, a self-built Linux server as router. Tinkering turned into calling.

Born 1980, first machine an Atari ST 520 with a high-resolution SM124 monitor. Games were scarce for the platform — so they were built, in GFA Basic. Text adventures with my own stories, Jump'n'Run clones in the spirit of Super Mario and Commander Keen, small tools that did what no product did. My father showed the first steps; the rest came from books, then local bulletin board systems, then the early internet. Lots of self-initiative back then — a constant that stayed.

When wider connectivity arrived, the first self-built Linux server moved into the basement: router and firewall in one, because the ISDN line wasn't paying for itself and household peace on the phone bill mattered. At night the modems chirped to swap files or chat with kindred spirits. While others consumed, I built — and learned that machines can do things they can't yet do, if you teach them. That tinkering turned into calling.

The reflex stayed: I'd rather build a tool myself than put up with one that doesn't fit how I work. Most recently a Git tool of my own, forq, replaced the classic client — tailored to exactly the workflow I need every day.

Milestones

A selection of the most formative engagements.

“Do it right, or don't do it.”

Discipline

Early forties, desk to road bike — and realized the mountains reward the same thing as the desk: keep going when it hurts.

In my early forties I noticed: two and a half decades of screen work charge a price I don't have to pay. Desk to road bike. What started as ‘just get out for a bit' became systematic endurance training — not just because it's fun, but because structure works: consistent preparation, long timelines, clear milestones.

In summer 2025 I finished the Ötztaler Radmarathon — 230 kilometres, 5,500 metres of climbing, four alpine passes in one day. What stood out wasn't the finish line, but the years before it: training plans, setbacks, constant adjusting, many hours in the mountains. It's how I take on an architecture project too — from the first sketch into production.

What comes after the finish line isn't rest, it's the next goal. For 2026, two new challenges are on the calendar: FUGA300 in June, ISTRIA 300 in October — 300 kilometres each, a different format than the Ötztaler, new demands on pacing and route knowledge.

Sport is also the tool that clears my head on difficult decisions. Twenty minutes running solves more than two hours brooding at the desk — and for years it's been my insurance against the stress level becoming chronic.

Private

Family on the Moselle, Kubernetes cluster in the basement, smart-home with high availability — because the lights shouldn't go out while I'm in a hotel.

At home there's my wife, two kids, and a Kubernetes cluster in the basement that has carried the family setup for years — smart-home, media, backups, a local LLM. What I build professionally, I often try out here first.

That the setup needs to be highly available didn't come without tuition: the day the home server died while I was on a business trip and my family couldn't switch on the lights in the kids' rooms, the lesson was unmistakable. A system doesn't belong to the person who built it but to the people relying on it.

And two kids growing up alongside it: Felicia (born 2014) builds her own games and stories in Scratch, Jona (born 2020) is into robots. The same curiosity I had sitting at the Atari — just a few decades later.

Sound like your world?

Let's talk about how I can help.

Start a projectCallView CV