Independent · Ad-free · Reader-supported
Free to read. Not free to make.
Every tutorial, article, and line of example code on this site is published without a paywall and without ads. This page is about what keeps it that way — and about the people who already help.
01 — The honest math
Professional work, published free
I'm a professional software engineer and consultant. The content here is held to the same standard as my client work: every tutorial is built as a real project, tested against current versions, documented step by step, and revisited when the frameworks move on. A single in-depth tutorial routinely takes days — and that's before the unglamorous bills behind it: servers, storage, build infrastructure, licenses, and the hardware everything is verified on.
None of that is a complaint. Publishing free, rigorous material is a deliberate choice, and I intend to keep making it. But “free to read” and “free to produce” are two very different things, and it's worth being honest about the difference.
So here's the deal, stated plainly and without a guilt trip: if an article or tutorial here has saved you an afternoon of debugging, taught you a technique, or helped you ship — it created real value for you. Supporting it isn't charity. It's paying for professional work you found useful, at whatever price you choose. And if you can't or don't want to, keep reading anyway. That's what the free part means.
02 — Ways to support
Pick whatever fits
Three options, in no particular order. Each one genuinely helps keep the tutorials and articles coming.
Ko-fi
Buy me a coffee
A one-time tip — no account, no subscription, any amount. The digital equivalent of getting the next round after a problem got solved.
Books & Courses
Buy the paid work
The most direct support there is. The books and video courses are the paid tier of everything published free here — and you get something lasting in return.
Spread the word
Share an article
A recommendation costs nothing and matters enormously. Send a tutorial to a colleague, cite an article, subscribe to the RSS feed.
03— Credit where it's due
The supporter who was there first
A support page would be dishonest if it only looked forward. One name has carried this work from the start, and it belongs here.
Supporter since day one
Thorsten Hindermann
Fellow developer Thorsten Hindermann has backed this work from the very beginning — the first tutorials, the first blog posts, the first books, and everything since. Not once, not occasionally: consistently, since day one.
Support like that is easy to underestimate. Knowing that at least one person reads carefully, buys the books, and comes back for the next piece is often the difference between publishing it and letting the draft die quietly.
What started as support has grown into something better: regular discussions over Zoom, developer to developer. It's a genuine exchange of ideas that sharpens the work on both sides — proof that supporting someone's writing can turn into a conversation worth more than the writing itself. Thorsten — thank you. This page exists in no small part because you proved early on that someone was listening.
04 — Tools partners
The companies behind the toolchain
Professional content needs professional tools. Two companies recognize community work with access to theirs — and everything published here is built with them.
MVP program
Embarcadero Technologies
Embarcadero — the company behind Delphi and RAD Studio — has supported this work every step of the way. As an Embarcadero MVP (Most Valuable Professional) since 2016, I'm part of a small group of community members recognized for teaching, writing, and speaking about Delphi — and Embarcadero backs that recognition with access to their full toolchain.
Every Delphi tutorial, book chapter, and code sample published here is built and verified with those tools. That access removes a real cost from producing free content, and it deserves to be named.
Ambassador program
GitKraken
GitKraken — the company behind the GitKraken Git client and GitLens — supports this work through its Ambassador program. As a GitKraken Ambassador, I advocate for their products because I use them every day — and GitKraken, in turn, provides access to their toolchain.
Every repository behind these tutorials, articles, and books is managed with their tools. Version control is the invisible half of publishing working code, and having the best tooling for it is support of the most practical kind.
05 — No obligation
The work stays free either way.
Nothing here goes behind a paywall, whether you chip in or not. But if something on this site earned its keep today, this is where to say so.