I've written a new book, and this one is quite different from my previous books. Instead of being a coding guide, this one is a guide to designing, building, shipping and maintaining real apps. It does include some coding, but the emphasis is on the process, not the code. As usual, I concentrate on macOS but the core principles apply to all Apple platforms.

I wrote this book for people who have done some tutorials, read books, watched videos, and who know some Swift and SwiftUI but are finding it difficult to make the leap from there to working on their own apps. It's also for more experienced developers who want to learn how to design and structure their projects to make them easier to maintain.

The book is completely written but is still being edited, so I'm offering a pre-release edition at a discount. You'll receive the complete book as a free upgrade when it releases in June, if you buy the pre-release.

You can buy the book from Gumroad and you can read the introduction and first chapter for free at Escape from Tutorial Hell Sample.

Apple's Worldwide Developer Conference is just weeks away, but I'm sensing a lot of apathy in the community. The company's relationship with third-party developers is at a low point.

We all know that Tim Cook and his senior people will stand up at WWDC and say how much they value their developers and boast about how much money they've paid out to them. Being so enthusiastic about the money is very strange - it's like a rent collector bragging about how much money he has given to the landlord when all he's doing is collecting the rent and taking his cut. And it's difficult to take Apple's apparent enthusiasm for their developers seriously given their behavior over the rest of the year.

Trust is a hard thing to gain. Apple used to have the developers' trust but now they've lost it. It's much more difficult to regain lost trust than it is to gain it in the first place. I have read many reports of talented developers leaving the Apple ecosystem because they can't take it any more. This is bad for all of us, but particularly bad for Apple.

I don't imagine that anyone at Apple reads my blog, but I have thought of some things I think they could do to improve their relationship with their developers.

I've just released Man Reader 2.1. Visually, this is very similar to the previous version, but there are a lot of quality of life improvements under the hood.

The most important feature of this release is that the app no longer crashes when typing fast into the search field. Sorry it took me so long to fix this, which was due to the way the app communicated between the AppKit list in the sidebar and the SwiftUI search field. SwiftUI lists have become a lot more performant, so I put a lot of effort into trying to make the entire app SwiftUI but in the end, it was just too sluggish so I reverted to AppKit, but with added traps to avoid crashing.

Recently, I was working with units and unit conversions in Swift. After a while, I then remembered that Swift has a built-in structure for doing this: Measurement. This article is an introduction to the power and usage of Measurement.

I have been running this blog since 2014 and it's seen several major changes along the way. I started with WordPress but it felt slow and clumsy, so in 2015 I entered the world of static site generators and transferred to Jekyll. That worked for a couple of years until Jekyll was updated from version 2 to version 3 which broke my setup. At that point I converted to Hugo which has worked fine for more than six years.

But as with Jekyll, updates broke my site and I didn't know enough about how it all worked to fix it. As a temporary measure, I reverted to an old version of Hugo which got everything working again, but this was not a long term solution.

After considering a number of options, I decided to try Eleventy and that's what you're looking at right now.