Java & J2EE consulting — one senior engineer, no middlemen

Twenty years of enterprise Java. No slide decks, no juniors, no surprises.

I'm Ferenc Turi. I design, build, and fix Java/J2EE systems myself — the person who reviews your code is the person who answers your email. If something's wrong with your project, you'll hear it from me before it gets expensive, whether or not it's what you wanted to hear.

~20 years of enterprise Java
4 countries: HU, AT, DE, BE
1 engineer — always me, not a bench
0 slide decks in the deliverables

How I work

Practical help across the project lifecycle

01

Reviews that name names

I read the code, not the roadmap slide. If a module is one bad merge away from unmaintainable, I'll say so — with the file and the line, not a maturity-model score.

02

AI-assisted, not AI-excused

I use AI daily and it's genuinely useful. What it doesn't get to do is ship code nobody on the team can explain. Every AI-assisted change still needs a human who understands it.

03

Practice over certificates

I hold a degree, not a wall of badges. What I bring is two decades of J2EE systems that had to survive contact with real users — a harder exam than any multiple-choice test.

What you can expect

A consulting style built around responsibility.

Bad news in week one

If your project has a real problem, you'll hear it before you've paid for a full engagement — not buried in a final report nobody reads.

Evidence over opinions

I'd rather read three real log lines than sit through a two-hour status meeting. Show me the system; I'll tell you what it's actually doing.

Not here to be liked by your Jira board

My job is to make your next engineering decision easier than it was yesterday, not to sound clever in the retro.

What I ship, I stand behind

You're paying for judgment, not a template. If something I built breaks, fixing it is on me — not a footnote in the contract.

Mission

Clear technical guidance without unnecessary ceremony.

I got into consulting because too many teams pay for advice they can never actually use. My job is to hand you something you can act on this week — a diagnosis, a fix, a plan — not a slide deck that ends up in a shared drive nobody reopens.

If you need an outside view on architecture, source code, AI-assisted development, or your delivery process, I keep the work concrete, testable, and something you can hand to your team on Monday morning.