Jacek SultanIT mentor · CTO · programmer
I teach programming, web development, software testing, Docker and working with AI. One-to-one and online, usually once or twice a week, on your own code and at your pace. Lessons are in Polish. By day I’m CTO at Dock, and I’ve been programming for about 15 years.
Orchestration for the year ahead
Mentoring
Programming, websites, testing, Docker, AI. We meet online, usually once or twice a week for 60 minutes. We work on your code, and between lessons you practice on your own, following a plan we’ll put together.
Sessions are held in Polish.
You tell me what you want to learn and where you are now. I tell you straight whether I can help.
We agree on the goal, the topics and the pace. Most often once or twice a week.
60 minutes of work on your code. After each lesson you get a note: what we did and what to practice.
Code, solid engineering habits and backend. From your first projects to career decisions at mid level.
Docker, Linux, CI/CD, Traefik and architecture decisions that a small team can maintain.
Web, WordPress, PrestaShop and digital accessibility in practice: from semantic HTML to audits and fixes.
Manual testing, API testing, Playwright, unit tests and BDD. From your first test case to automation in CI.
AI in everyday work, workflows, integrations, APIs and agents. Also for people who don’t code.
You don’t need a ready-made plan. We’ll build it together on the first call.
Rated 5.0 out of 5, 1 review on e-korepetycje.net (opens an external site)How a decision takes shape
01 Context
We have a dozen or so applications that have to run together on several servers and update without downtime. Before I choose a tool, I write down exactly what the problem is and who will maintain the solution afterward.
02 Options
Kubernetes, Docker Swarm, a managed PaaS. Each one solves the problem. Each one costs something different.
03 Criteria
How many people will maintain it, what it costs, how much it has to grow. I judge the options against our situation, not their popularity.
04 Trade-off
Kubernetes is too heavy for our team, a PaaS too expensive at our scale. I write down why, so I can come back to it when conditions change.
05 Decision
We stay with Swarm for 12 months. We’ll revisit it when we need per-service autoscaling.
06 Code
Only now do I write the configuration. The decision lives in the repository, next to the code that follows from it.
Read the full analysis$ docker stack deploy -c stack.yml appCreating service app_apiCreating service app_web✓ update_config: start-first, rollbackWhat I work on
Backend and web applications that are still maintainable a year later. I treat code quality as a cost someone will pay eventually, so I’d rather pay it deliberately.
System design, Docker, CI/CD, security. Operational decisions the team understands and can handle at 3 a.m.
From a client’s need, through scope and budget, to a shipped product. Talking about cost is part of talking about technology.
WCAG in practice, not on paper. Automating work and using AI models sensibly, where they save time rather than just look impressive.
Projects
Three places where I make decisions every day. Scroll sideways.
See what I’m working onP/01 · Technology company
P/02 · SaaS product · digital accessibility
P/03 · SaaS product · monitoring and security
Latest
The biggest cost isn’t the model. It’s checking what the model produces. Here’s the simple calculation I start every automation conversation with.
Swarm isn’t fashionable, but in a small team it often beats Kubernetes. Here’s how I weigh the choice and how I can tell it’s time to change it.
A green result from an automated tool only means it didn’t find what it knows how to find. Here’s what the rest of the audit looks like.
Twenty minutes is enough to work out what you want to learn and whether I can help. For anything else, like a consultation or a recording, just write to me.
Gdańsk, Poland · remote / online