I’ll be honest: writing in public is uncomfortable. English is not my first language, and turning years of hands-on work into clear technical writing is its own skill. I’d rather start now and improve than wait for a perfect first post.
So here is what I’m bringing to this blog.
Experience worth writing down
I have more than ten years building software across very different domains - industrial systems, e-commerce, gaming platforms, payments, and travel. The most useful thing I can share is not syntax; it’s the decisions, trade-offs, and failure modes I’ve seen repeated across teams and projects.
Why I’m sharing it
I enjoy explaining systems, and I do it regularly. A couple of examples:
My team also won HackYeah, which taught me how much you can ship when scope, focus, and execution line up.
What to expect here
Practical engineering notes: architecture decisions, AI used as a real tool, testing strategy, and the reasoning behind production systems - not tutorials that stop at “hello world”. If that’s useful to you, stick around.
Michał Gacek - Tiptopdesign