Clarity over cleverness
If it needs a paragraph to explain, it probably needs a refactor.
I'm Jason — a Java backend developer building services, APIs and infrastructure that stay fast, clear and reliable long after the launch party.
@RestControllerpublic class JasonController { private final Developer jason; @GetMapping("/profile") public Developer profile() { return jason; }}
I care about the unglamorous parts: clear boundaries, honest APIs, predictable deployments and code the next person can actually read.
I'm Jason, a 23-year-old backend developer based in Germany. Most of my time goes into the JVM — designing Spring services, modelling data, and making sure the boring path through a system is also the reliable one.
I like work where correctness matters: APIs that behave, data that stays consistent, builds that don't surprise you at 2 a.m. When something is slow, I measure before I touch it. When something is complex, I look for the simpler shape hiding underneath.
If it needs a paragraph to explain, it probably needs a refactor.
Predictable infrastructure beats heroic firefighting every single time.
Performance work starts with numbers, not opinions.
No buzzword bingo — this is the stack I use to design, build and ship backend systems.
A few projects where architecture, performance and clean delivery mattered more than the landing page.
A Minecraft plugin engineered for performance under load — clean architecture, efficient event handling and a codebase that scales with the server.
A digitalisation platform that replaces paper workflows with automated processing pipelines — from intake to completion, without the filing cabinet.
A low-latency audio streaming backend that pushes real-time data from Java services to connected clients — without buffering drama.
A modern web dashboard for deploying, managing and monitoring server instances in real time — less SSH, more visibility.
Want the architecture behind one of these? Ask me — I'll walk you through it.
Map the domain, the constraints and the failure modes before writing code.
Shape the boundaries: data model, API contracts and the boring happy path.
Small, tested increments. Clean layers. No surprise dependencies.
Load, logs, metrics and edge cases — until production is uneventful.
Whether it's a new service, a stubborn legacy system or an API that needs to behave — send me a line. I'll reply with a straight answer.