While I am still convinced the unified logging system is great, the masking of value interpolations gets into my way often enough, too. The way to unmask those values has changed drastically from macOS release to macOS release.

SwiftData is very neat. Concise, simple and fast. I quickly hit show stoppers, though.

I just want to share a minor inspiration which might help in daily business with unit tests.

While making my first experiences with SwiftData, I also used @Attribute(.unique) on a model property. I expected model insertion to throw an error or crash in case this constraint is violated. The actual behaviour was rather surprising.

With the introduction of Swift macros in 2023, I have came across a few situations in which they have become useful. One is the reduction of boilerplate code. In example the automatic declaration of a Logger property on a type.