Services
Portal, business application, integration, app, or the piece of software that doesn’t exist yet. Which technology? That depends on your environment, on what’s already there and on the people who’ll maintain it later. And because I work with AI tools, you get the pace of a small team. The invoice says one developer.
Take a sounding
How deep do you need to go?
Software has layers, and most providers live in just one of them. The lead shows what I do at each depth.
-
0 m
Surface
The thing your business unit opens first every morning. Fast, accessible and built so nobody needs a training course first.
Angular · Vue · React · HTML/CSS
-
5 m
Logic
Business rules, workflows, interfaces to other systems. The part that knows your business and therefore deserves documentation.
Java/Spring · Node · PHP · REST/OpenAPI
-
15 m
Data
Models you still understand in five years. Migrations that don’t keep anyone up at night, indexes before anyone complains it’s slow.
SQL · PL/SQL · MongoDB · Redis
-
30 m
Operations
Roll out, monitor, restore. So you can sleep at night, and so can I.
Docker · Jenkins · Linux · monitoring
-
45 m
Bottom
Down here lies the system nobody wants to touch any more, and without which the business stops. I touch it. Afterwards it still runs.
Java 6 · PL/SQL · Excel macros · a manual from 2009
Bottom reached. It goes no deeper. Everything above, I do.
Drag, scroll or use the arrow keys
Surface
What your users see and use.
-
01
Web applicationsSingle-page and server-rendered applications with Angular, Vue or React. Fast, accessible and maintainable, not just pretty in a screenshot.
-
02
Motion & interactionMovement that explains something. Scroll-driven sequences, WebGL and Canvas, animation with weight and inertia. This site is one example.
-
03
Design implementationFigma designs become responsive code, with colours and spacing as tokens rather than numbers scattered through the stylesheet. If the blue changes later, it changes in one place.
-
04
Progressive web appsInstallable, offline-capable apps from one codebase. As an Android app via Capacitor when needed.
Depth
What your users never see and need every day.
-
01
Back end & APIsServices in Java and Spring, Node or PHP, with documented interfaces (REST, OpenAPI) and data models your next developer will understand too.
-
02
DatabasesRelational and document-oriented: SQL, PL/SQL, MongoDB. Migrations, indexes and consistency, even when the network drops for a moment.
-
03
Real-time & live systemsWebSockets, state sync across many clients, deterministic computation. For live shows, multiplayer and anything that has to stay traceable.
-
04
DevOps & operationsDocker, Jenkins, reproducible deployments, monitoring. So “works on my machine” turns into “works on yours”.
Engagement models
Depending on what you need and where the project stands. The model changes nothing about the code, only the invoice.
| Model | For | Billing |
|---|---|---|
| Contracting | an extra developer on your team, ongoing development | by time, hourly or daily rate |
| Fixed-price project | clearly scoped product or feature | fixed price based on a specification |
| Architecture & consulting | design, reviews, DevOps setup | day or package rate |
| Live & broadcast tech | overlays, show systems, event operation | project or event price |
Engagement directly or via staffing agencies. Remote or on-site across Germany, Austria and Switzerland. Day and project rates on request.
Technology
My everyday kit, with the year I started working with each. If you’re on a different stack, I’ll get up to speed. A new framework is quicker to learn than your business.
| Area | Tools | since |
|---|---|---|
| Languages | Java, TypeScript, JavaScript, PHP, C#/.NET, Lua | 2014 |
| Front end | Angular, Vue, React, HTML5/CSS/SASS, WebGL/Canvas | 2017 |
| Back end | Spring, Node.js, Express, REST/OpenAPI | 2014 |
| Data | SQL, PL/SQL, MongoDB, SQLite, Redis | 2014 |
| Operations | Docker, Jenkins, CI/CD, Plesk/nginx, Linux | 2017 |
| Real-time | WebSockets, state sync, deterministic simulation | 2019 |
| Practice | Scrum, Jira, Git, code review, test automation | 2015 |
Six pages, six jobs.
What the sections above list in keywords, these pages spell out: one page per job, with typical assignments, the technology behind them and a proof you can go and read.
- Back end & Java The part of your software nobody sees and nothing works without. I have been building it since 2014, mostly with Java and Spring.
- Web front end The interface your people work with for eight hours a day. It doesn’t have to win awards, it has to still be bearable in hour eight.
- Integrations Two programs that need the same data and know nothing about each other. In most organisations that is the actual job.
- Business applications Off-the-shelf software covers eighty per cent. The remaining twenty is the part that makes your organisation different from the next one.
- Legacy systems The system nobody wants to touch any more and without which the business stops. I touch it.
- Operations & DevOps Software isn’t finished when it works, it’s finished when it runs on your side and somebody there knows how.
What’s on your mind?
Whether it’s a specific project or just a question for now, write it down the way you’d tell a colleague. You’ll get a reply from me, not from a mailbox.