This is not an April Fools joke. This is a real project I built in an afternoon using Claude Code and Delphi. It is a command-line tool that scans my PC for installed games, identifies their save file locations, and creates backups with optional S3 upload. The entire implementation was generated by Claude based on my specifications, and it compiles to a single native executable with zero dependencies beyond sqlite3.dll. This is the power of spec coding.
There are a handful of tools out there for backing up PC game saves. They all share the same problems: bloated UIs, slow performance, confusing workflows, and the kind of feature creep that turns a simple task into a chore. I wanted something different. Something fast, something I control, something that just works.
So I built my own. In an afternoon. With Claude Code as my pair programmer.
The Delphi community has strong opinions about AI — and I get it. Privacy concerns, code quality worries, the instinct that real developers should not need a machine to help them write code. I have heard every argument in the book, and honestly, some of them are fair. The skepticism is real, though the tide may be turning. Still, the doubters outnumber the converts, and I am not here to pretend otherwise. But after what I just witnessed on a real-world migration project, I think even the skeptics will have a hard time arguing with the results. This is not about replacing developers — it is about what happens when developers stop fighting the tool and start using it.
A customer approached us with a legacy desktop application built in Delphi 7. Let that sink in for a moment. Delphi 7 — released in 2002. No Unicode support. No HiDPI awareness. Running on Firebird 1.5 — a database engine so old its last update predates the iPhone. The application had been serving its purpose for over two decades, but the world had moved on. No responsive design. No web access. No mobile support. Customers had been begging for a web-based solution for years, but the cost and complexity of a ground-up rewrite in the legacy stack — let alone migrating to a modern platform — had always been prohibitive.
The target: a full-stack TypeScript application built on Next.js with server-side rendering, a component-based UI, Prisma ORM for database access, and a responsive design that works on both desktop and mobile devices. Not just a facelift — a complete architectural transformation from a Win32 desktop application to a modern, deployable web platform.
This was not a toy project. It involved user authentication, role-based access control, property management workflows, incident tracking, image handling, complex relational data models, and a migration pipeline to move real production data from the legacy Firebird database. The kind of application that, in any traditional development shop, would require a team and a timeline measured in months — which is precisely why it had not been done in over twenty years of customers asking for it.
The other day I saw a post on a Delphi developer forum. A fellow developer had been struggling for days trying to convert a bitmap to grayscale. Days. He had tried multiple third-party components, downloaded libraries, read through outdated documentation, and was still stuck. The forum thread was filling up with suggestions for yet more components to install, each with its own quirks, licensing, and version compatibility headaches.
Mark J. Price has done it again. After his excellent C# 14 and .NET 10 – Modern Cross-Platform Development Fundamentals, I could hardly wait for this third edition of Apps and Services with .NET 10 to be released — and it absolutely does not disappoint. This is the third book in Mark's four-volume .NET 10 learning quartet, and it is exactly where the series hits its stride: broad in scope, practical in approach, and packed with real-world examples for every single topic it covers.
If you are a .NET developer looking to move beyond the fundamentals and into the technologies that actually power modern applications and services, this book belongs on your desk.
I'm thrilled to announce that I'll be speaking at TMS Training Days 2026 in Rotterdam, and I hope to see you there! After successful events in Lille and Bruges, the TMS team is bringing this incredible two-day developer conference to the Rotterdam Marriott Hotel (right across from Rotterdam Central Station) on April 23-24, 2026.
Here's an interesting fact: When I got deeply involved in the Delphi community back in 2004, everybody was telling me "Delphi is dead." The hot new thing was .NET, and conventional wisdom said anyone still writing in Delphi was living in the past.
Guess what? It's 2026, and Delphi is still in production, still being actively developed, and I'm still making money writing code in Delphi. In fact, my entire consulting business is built partly on helping companies maintain and modernize their Delphi applications.
I learned something valuable from that experience: premature obituaries and hype cycles are terrible guides for technology decisions. Longevity comes from solving real problems reliably, not from being the hottest thing on tech Twitter.
The no-code movement is having its moment. Articles proclaim its death, its rebirth, its transformation. But amid all this noise, there's a critical distinction being lost:
Rapid Application Development (RAD) is not no-code, and the difference matters more than ever.
I've been building Windows desktop applications with Delphi for three decades. During that time, I've watched trends come and go—from the CASE tool revolution to today's no-code platforms. And I've learned something important: there's a vast difference between tools that eliminate coding and tools that accelerate coding through intelligent design.
I started with Delphi before most developers today wrote their first line of code. Over 30 years, I watched Borland rise, worked inside the company, and built a career helping others master the platform. I've created hundreds of videos, spoken at conferences worldwide, and earned recognition in the Delphi community.
But I'm not writing this to reminisce. I'm writing because the world has fundamentally shifted, and pretending otherwise helps no one.
The traditional setup—a developer at a desk, building Windows applications that run on office PCs—is no longer the default. People work from phones on trains. They access business systems from tablets in warehouses. Executives approve invoices from airport lounges.
The desktop isn't dead. But it's no longer the center of gravity.
