Development
I build applications, services and integrations designed to be operated as much as demonstrated: tested, observable and straightforward to deploy.
Freelance IT specialist
Hands-on engineering and delivery, by one person.
I work as engineer, analyst, coordinator or manager, whichever a project needs. I build software, rework what has outgrown its design, shape architecture and keep delivery honest.
Services
What I do
Rework
I take over systems that have outgrown their design, then untangle, modernise and stabilise them while they keep doing their job.
Architecture
I put structure and decisions on paper: system boundaries, integration styles, hosting and deployment models a team can live with for years.
Project oversight
I give delivery an independent technical eye: reviewing plans and progress, checking suppliers' work and keeping scope, quality and risk honest.
Roles
Many hats, one person
Small teams rarely need four more people. They need one who can switch between these as the work changes.
Engineer
Designs, builds and repairs the thing itself.
Analyst
Turns vague needs into clear, testable specifications.
Coordinator
Keeps people, suppliers and moving parts pointed the same way.
Manager
Owns scope, plan and risk, and says so early when they slip.
Scope
The shape of the work
Delivery has covered much more than writing code. These are the situations I am used to stepping into, described by what they asked of me rather than by whom they were for.
People
Building, merging, handing over and onboarding teams. Hiring, interviewing and running internships. Growing juniors into regulars and seniors into tech leads.
Delivery under pressure
Multi-year programmes, releases coordinated across several teams, audits, restructurings and the occasional fire drill, with the plan kept honest throughout.
Engineering depth
Performance and observability, large framework migrations, forecasting and simulation-style systems, platform work, upgrade automation, cloud and the cost of running it all.
Before the build
Judging feasibility early, adapting a product to a client's needs, and localising it for a market.
Two languages
Fluent in Polish and English, including a background in professional translation, so intent survives the trip between the two.
Still hands-on
I still write code, and I now delegate to AI assistants the way a lead delegates to a team: small tasks, clear boundaries, everything checked.
How I work
Plain engineering, done carefully
Small, reviewable steps
I deliver changes in pieces that can be read, tested and reversed, so progress stays visible and risk stays low.
Operable by default
Health checks, repeatable releases and a way back belong in the first version, not in an afterthought.
Decisions on paper
I write trade-offs down where the next person will find them, so knowledge outlasts any one engagement.
Working together
Ways to engage
Every engagement is shaped to the problem. These are the usual forms.
Embedded lead
I join a small team as both technical lead and manager, owning plan, quality and people while still contributing code.
Interim and handover
I cover a gap in leadership, steady the work, and hand it over cleanly so nothing depends on me afterwards.
Independent review
I give a plan, a codebase or a supplier's work a second, unattached technical opinion, in writing.
Defined delivery
I take a clearly bounded piece of work from analysis through to something operable and documented.
In the open
Tools, musings and side projects
Things I make and keep in public: tools I needed, experiments, and thinking out loud about how software work gets done.
Loading…