About me

I started in operations, not at a computer. Staffing agencies, production plants, personnel administration. Working time and invoices in SAP, customer data in CRM systems, recruiting construction crews, planning around 260 people across seven departments of a multi shift plant, transport, accommodation and the paperwork with German authorities.

That decade taught me the part you cannot learn from programming alone: what actually happens inside a company between the systems, and how much of it is people retyping data from one window into another.

I plan fibre networks for a German company, from Szczecin. Network data in QGIS and AutoCAD, documentation, tickets and customers in a CRM, correspondence in German.

On top of that come scripts and small programs written for one specific problem: so that data from two systems can be compared, so that a report builds itself, so that an import does not need fixing by hand. That kind of analysis also surfaces plenty of errors in the data itself. They used to be caught by eye, one at a time. Now I correct them with a click.

I cannot stand repetitive work. Somewhere around the third time I did the same thing, I would sit down and arrange for it to happen on its own. Every company I have worked for kept something durable afterwards: an integrated document flow, automatic emails, a data migration, two systems that had never spoken to each other and then did.

The people who came after me simply had it easier, and that gives me more satisfaction than ticking tasks off a list. My own products come from the same place. Exam papers that mark themselves and a planner for field crews are the same idea on a larger scale: make the work easier instead of adding to it.

For three years I have been designing websites and applications: from simple one page sites to systems that come close to a CRM or an operations planner in what they do. I know the stack, I choose the architecture, I test, I deploy, and I answer for what runs.

I do not pretend that I type every line myself. The code is written with AI tools, and I am the one who knows what has to be built, checks whether it works and carries it when it does not. Most of the industry works this way now, it is just rarely said out loud. For the client one thing matters anyway: whether the product works and whether there is someone who answers for it.

I follow sport, football above all, and I look at it the way I look at any data set. Betting markets are the fastest public data I know. A price moves in the second a break point is lost, a red card is shown or a dart misses the double. No exchange reprices that quickly off a single event.

So it became my training ground for APIs and data processing: pulling complicated statistics, stitching them together across sources, and watching how a model turns an event into a number. Time is a variable of its own. The closer to the final whistle, the more the same scoreline means, and the probabilities keep moving even when nothing happens on the pitch.

On Algebra i Spółka a good part stays open: the exam papers that mark themselves, the games, the calculators. A student sitting down to a problem at ten in the evening needs the solution, not a price list. The more young people practise thinking logically, the better for everyone, me included.

I have been donating blood for over fifteen years, more than twenty litres by now. In 2025 it came with a national medal for services to public health. The thing itself is simpler than that sounds: an hour every few weeks.

I have played guitar for many years, including on stage, in a duo whose site I ended up building. Chess and books take up the rest. My German comes from living and working in Germany, not from a course. English is enough for work and documentation, and Spanish is new enough that it still stops at ordering coffee.