Toomas Vahter

@toomasvahter
186 Followers
100 Following
195 Posts
Love programming in Swift
Indie appshttps://augmentedcode.io/portfolio/
Bloghttps://augmentedcode.io/blog
Toomas VahterDec 22
Dimitri BouniolDec 22

TLDR, stop using ISO8601DateFormatter, it's pretty slow compared to the modern FormatStyle alternatives #SwiftLang

https://gist.github.com/dimitribouniol/aea2e12be8e6c613891f96de856dfbfb

Toomas VahterAug 13, 2025
Nick SloanAug 12, 2025

For the past year, I’ve been using Swift to build web projects, mostly for Studioworks. I’ve gotten some questions about why we made such an unconventional choice, so I wrote up some of the things we’ve been enjoying about Swift for web projects.

https://nicksloan.com/posts/swift-for-the-web/

Swift for the Web

Show threadToomas VahterJun 20, 2025
Maybe I just need to accept this and just navigate to Finder when I need to delete a file from the local package in the demo app 🤷‍♂️ or opening the package through Package.swift. So odd it worked so well years ago and not anymore.
Show threadToomas VahterJun 20, 2025
Even if I create a workspace, I can’t find a way to add the Swift package of the current repo (aka Package.swift at the root of the repository)
Toomas VahterJun 20, 2025
Sad that Xcode does not allow creating demo app project in a Swift package repo in a way where the package is grouped together with the project. Adding as local package dependency is the current way, but not sure why Xcode does not allow deleting files from the local package. Editing is alright, but why can’t I remove files 🥲 Can’t find a workaround for this setup.
Toomas VahterJun 14, 2025
Craig HockenberryJun 12, 2025

Approachable concurrency in Swift is such a welcome change.

It starts with the assumption that app developers have a simplified understanding of the language and its capabilities. Then it provides a way to extend that knowledge as their needs change.

So much better than "here's a hard hurdle you have to jump over to start".

Congrats & thanks to all who worked on it!

Toomas VahterMay 27, 2025
Chris EidhofMay 27, 2025
Vibe coding is not a new thing. I've been using Xcode's "Fix All Issues" for like 15 years (probably the current generation of vibe coders was still binge watching paw patrol back then). Gets you the same results: the errors are gone but nothing really works.
Toomas VahterMay 27, 2025
Dave DeLongMay 25, 2025

It's another one of those days where #Xcode is making me want to throw my computer through the window and go become a hermit.

Today it's the fact that if you open a project from an unwritable location, Xcode will pop up this alert EVERY THREE SECONDS UNTIL YOU CLOSE THE PROJECT.

There is absolutely no way to browse code. No way to see how things are being used. No way to stop Xcode from trying to *write data* just for OPENING THE PROJECT. Absolute utter insanity.

Toomas VahterApr 24, 2025
Dave DeLongApr 23, 2025

All I want for #WWDC is for Xcode to correctly report build status.

Literally nothing else. Fix this and I'll stop complaining about stuff for an entire year. PLEASE.

Other fixes would be nice too, but the #1 thing an IDE needs to do is show correct information. If it can't do that, it doesn't matter what else it can do; it’s not trustworthy.

Toomas VahterApr 21, 2025
Cihat GündüzApr 21, 2025

New article: Why your #Swift error messages look like gibberish—and how to fix them once and for all! 💥

"The operation couldn't be completed. (YourApp.YourError error 0.)"

Sound familiar? This article shows you how to escape the Objective-C error legacy. 👇
#iOSDev #ErrorHandling #BestPractices
https://www.fline.dev/swift-error-handling-done-right-overcoming-the-objective-c-error-legacy/

Swift Error Handling Done Right: Overcoming the Objective-C Error Legacy

Tired of cryptic Swift error messages like '(YourError error 0)'? Here's how to fix them for good—with clarity and elegance.

FlineDev Blog – Insights on Swift, Xcode, and Apple Development