I’m the healer that will clean up the Reapers sneaking behind you and snipe the Bastions and Widowmakers that you’re too important to keep from picking off your team.

That moment where you happily exclaim “I have test failures!” because that means your build is finally running through again after build system changes. 😳

If you installed Catalina on a second partition but your internal one still notifies you of the Catalina upgrade, you can “Reset to Defaults” using the “More…” link on the left under “This Mac is enrolled in the Seed Programme”.

Hauptproblem an Dr. Mabuse, der Spieler heute wären Handys (könnte man aber leicht anpassen), und die Kameraführung (ist historisch bedingt halt sehr statisch). Und natürlich müsste man das Timing straffen, ist ja kein Stummfilm mehr.

Schaue gerade wieder Doktor Mabuse, der Spieler … den film könnte man unverändert als Tonfilm neu auflegen und er würde heute noch funktionieren.

Wenn man dann noch ein paar Updates vornimmt, wäre das wieder ein Spitzenfilm.

Even if it’s for pride week, I don’t like my apps (ab)using notifications for announcements that don’t actually notify me of any events in the app.

Swift style Q: My API currently is query { expression }.results() but internally uses a builder on which query() calls build(). I want to allow setting properties on the builder a la

query { expression }.ordered(.descending).build().results()

The extra build() irks me. You too?

I wish I could sort Xcode’s error list by error type. So that if I just made a function throw and now have 5 dozen “call can throw, but is not marked with try” messages I could easily do them in one go.

Given SwiftLint is such a stickler for details, I’m surprised it says “5 characters or less” and not “5 characters or fewer”.

Characters are countable, unless they’re GoT characters and have been beaten to a pulp…

Swift’s Opaque Types seem to basically be the equivalent of id⟨MYProtocol⟩ in Objective-C, right?

Someone on this morning’s podcast said “Ha-ha-ha-Hamish” and now I have the song “Tränen lügen nicht” (Maybe better known via Mark Oh’s “Tears Don’t Lie”) stuck in my head.

What can I say, it’s a catchy tune :D

Y’know, Instruments’ Time Profiler would be much less confusing if it didn’t mix seconds and milliseconds (I see 1s and go “oh those 400ms below it are larger than the 1ms”). Also if it had back and forward buttons when drilling down stack backtraces.

Anyone have other solutions than “not invented here” syndrome for malicious code in widely-used packages?


We don’t solve malicious code injected into packages by not re-using components just because s/o else wrote them.

If you have code in pull requests that you don’t know what it does, maybe we shouldn’t accept it? Maybe we shouldn’t rely on volunteers for critical infrastructure?