I found the documentation extremely lacking last time I looked at Swift 2 or 3 years ago. Any changes there? Or perhaps there’s somewhere outside of Apple’s own docs I should have been looking?

I would use reportMissingData

Agreed, report feels clearer as the verb “record” is more about permanent storage and later reference.

Or even just reportMissing? Depending on what’s happening around call sites, I often find I can drop generic stuff like “Data” and it’s just as clear, especially when looking at a function signature. For instance:

func reportMissing(data) { ... }

It attracts passionate and clever people, but as a result comes with a (rightful) reputation of being hard/expensive to hire for.

Worked at a Scala shop for a while. It was interesting as an outsider to see exactly that play out (I’m a diehard Unix hacker type, love Go etc.). There were some brilliant minds who really seemed to “get” the Scala thing. Then there were others who were more run-of-the-mill Java developers. Scala and the JVM makes all that, and everything in between, possible. With so many Java projects around, the Java devs would come and go depending on team/company factors like job cushiness, salary, or number of days in the office. But the more Scala-leaning people hung around. They made a huge impact on how projects were run.

The bosses would often talk with me about how hard it was to find those people. From a business perspective, they said it was absolutely worth the effort to find the Scala people despite operational overhead of the rotating door for the armies of Java devs.

The Philosophy section has quite a few wonky arguments; I’d skip it altogether.

Guidelines is pretty succinct and has many rules-of-thumb that almost any software would benefit from. That’s including CLI, GUI, libraries – even hardware if you take a bit of a step back.

I often like reading his older pieces. I forget how long he’s been at it for. Here’s one making fun of Apple almost 10 years ago: https://www.theguardian.com/technology/2015/feb/13/if-dishwashers-were-iphones

Ever wanted to feel what it was like to be on the inside of a microwave? Well, now you can!

The reason think that’s good is that companies that you would be looking for would not be easy to find in job boards because the flashy big-spend ones would show up the most. A recruiter would have easy access to the other ones, and might be happy to find somebody who actually wants to take them.

Haven’t thought about it like that before, but that makes sense. Perhaps because I had a couple of mediocre experiences with recruiters I’ve mostly avoided them since. But as I get more focussed in my search that might make it easier for a recruiter to go hunting, too.

Thanks for the reply