Consultant, developer, teacher
I build websites and information systems that outlive a single quarter.
I help companies and individuals turn ideas into real software — from a simple presentation to an internal system people actually use. I teach programming and consult when you want a straight answer instead of consultant ping-pong.
What I do
Three ways I can help. One person, three sets of questions, one email to get started.
IT consulting
An independent outside view — from technology choice to architecture review. No "we've always done it this way." Let's find what actually works for you.
Custom development
From a one-page presentation to the information system holding your company together. I own the work from design through deployment to the maintenance.
Teaching programming
I teach people to think about code, not just copy it. Good for beginners, juniors at your company, or enthusiasts who want to finally understand why it doesn't work.
Code that still makes sense a year later
One person, no ball being passed between five specialists. I've done both greenfield projects from an empty repo and years on a corporate system used daily by real people — so I can build new things as well as work in the so-called brownfield: modernizing a running system without having to take it offline for a week.
What I can build
Custom internal systems
From the five Excel sheets running your business to a proper internal system with users, roles, and reports. Usually where off-the-shelf doesn't fit and the manual work is starting to hurt.
Web apps and products
You have an idea for a product or service and need it up and running. Frontend, backend, deployment — the whole chain, one person, one line of accountability.
Brownfield modernization
A running system that needs to be rebuilt while it's live — no downtime, no tiger team parachuting onto a greenfield. Gradual replacement that doesn't break what's already working. Exactly what the corporate world teaches you every day.
How we can work together
Fixed scope
You know what you want. We agree on scope, price, and timeline. Fits when the ask is clear and both sides want certainty.
Build and hand off
From design through deployment to training your team. For when you want it done and maintained by your own people.
A few hours a week, long term
When a project is running and occasionally needs a feature added or an eye kept on it. Fits when you're not in a rush but want someone around who understands it and will come back to it next week.
What happens after launch? It depends. On some projects I stay quietly in the corner and tweak things now and then; on others I hand over the docs and wish you luck. It's not a package, it's a conversation.
A second pair of eyes, before you commit
Sometimes an hour with someone from outside saves months in the wrong direction. Everyone eventually gets attached to their own code — your team, your vendor. After a while you stop seeing what's off about it. I come in with no history, read it without bias, and tell you straight what I see.
What I can help with
Architecture review
You're picking a stack, drafting a design, or you got a vendor proposal and want an independent read on it. I'll ask before production does.
Codebase audit
Brownfield diagnostics. What's fine, what's risky, and — most importantly — what to touch first, whether for security, performance, or just so you can still work with it tomorrow.
Light retainer
A few hours a week on call for your team. Review a PR, unblock, talk through an architectural decision. Good fit for smaller teams that don't have a full-time senior.
Corporate work pays the bills, so consulting happens in the time that's left — don't expect 40 hours a week. That's exactly why I treat whatever I take on with focus. Short, sharp engagements usually work better than sprawling long-term ones.
I'll teach you to think, not to copy
Programming isn't a collection of incantations from a tutorial — it's a way to break a problem down into parts you understand. That's what I teach. Syntax is easy; the thinking behind it takes work, but it can be learned.
Who it's for
One-on-one lessons
Career changers, juniors moving from "copying from StackOverflow" to "actually getting it," or enthusiasts who touch code in the evening. The pace adjusts to you, not to a fixed curriculum.
Company team training
A structured program for your team. E.g. "Angular for five backend devs in six weeks" or "TypeScript for juniors so their script finally has types." We agree on goals, schedule, and format (online, on-site, or a mix).
I also teach at a university, so I'm used to explaining things clearly and more than once. Bonus: if I can't explain something, it means I don't understand it well enough — and that keeps me moving forward.
Who I am
I'm an IT professional. By day I work on a large in-house information system — from database to UI — and see what holds together in software and what falls apart after a year.
Outside the corporate walls I help smaller companies and individuals build what they need: websites, small systems, automations. I teach occasionally, because explaining things plainly is the quickest way to find out whether I actually understand them.
I work mostly with Angular, TypeScript and Kotlin. But a stack is a tool, not a religion — I use what makes sense for the problem.
How I work
The portfolio is still coming together — most of my work lives behind closed corporate doors. For now, instead of screenshots, this:
Works > trendy > traditional
I build things that work. Not necessarily the newest, not the "we've always done it this way" ones either. The technology follows the problem, not the conference hype.
Full-stack ownership
Frontend, backend, data layer, deployment. I don't hand the ball to five other people — I usually see the whole path from UX to SQL plan.
From the corporate trenches, not a tutorial
I work every day on an in-house information system with real users and real requirements. I know what software that outlives a single quarter looks like.
Plain language
Teaching programming taught me one thing: if I can't explain it, I don't understand it. So you get straight answers, not marketing fluff.
Get in touch
The shortest route to an answer is email. I usually reply by the next business day. LinkedIn works too, if you want to skim the profile first.