This is the biggest career risk of 2026.
I'm seeing this problem first hand.
"Meat proxies" don't review code when asked. They merely ask AI to do it.
"Meat proxies" don't understand their own code. When asked about it, they have to ask AI to explain it.
"Meat proxies" don't use their own judgement. They defer all decisions and taste to the AI.
Sure, use AI. But don't overdo it.
Be human.
"Anthropic, OpenAl and Google release their new models with high quality from day one then slowly nerf them until the next model, so when the next model hits, its perceived as a bigger jump than it actually is"
sounds right what's happening
🔺iPhone models announced today include Memory Integrity Enforcement, the culmination of an unprecedented design and engineering effort that we believe represents the most significant upgrade to memory safety in the history of consumer operating systems. https://t.co/ule9gaXzc1
Just launched fully automated localizations on String Catalog! 🎉
Now, each time you push to a specified branch, your strings are synced, and a PR with new localized strings is opened automatically (if needed). Super proud of this feature—it’s a huge time saver and works in the background fully automated.
Crowdstrike Analysis:
It was a NULL pointer from the memory unsafe C++ language.
Since I am a professional C++ programmer, let me decode this stack trace dump for you.
Check out this new feature of Swift 5.9! 😀
You can now use `switch` as an expression, making it much easier to dynamically set the value of a constant 👌
Xcode 15 comes with some great improvements in the debug console. I'm particularly excited about the new filtering functionality for logs, so I summarized the changes and how to best take advantage of them in my new blog post: https://t.co/IJGcdu5zid
I can't even thank enough of how my Kintsugi eased my daily job with Xcode
https://t.co/GepVy23aBo "A tool to automatically resolve Git conflicts that occur in Xcode project files"
About 9 years ago, I pushed a bug to Tinder that caused an on-launch crash to millions of users worldwide.
I built on the expectation that -[UITableView visibleCells] returned its results sorted in ascending order by section then row. (0: S0R0, 1: S0R1, 2: S1R0, etc).
It's an an easy psychological trap to fall into: That's a reasonable sorting scheme! The return value is an NSArray, not an NSSet!
And, to my defense, UIKit *does* sort it that way most of the time... except when it doesn't. And with millions of DAU, that 'small' deviation quickly becomes meaningful. (IIRC, it was sorted differently 20-30% of the time, maybe?)
Chris Payne (the CEO at the time) sat down in front of me sweating and basically begging me to get it figured it out. Soon after, I got to the bottom of it, shipped an expedited fix, and it was resolved. 😮💨
A few years later, Apple added a clarification to the documentation *specifically about this*. Sweet, sweet vindication! Though, in recent years, that clarification has disappeared for some reason. Be careful!
https://t.co/pBj0H9Q76M
Coming in Swift 5.9, package will be a new access modifier in the language.
The Swift team at Apple approved the Swift Evaluation proposal SE-0386 which includes adding a new access modifier called package to allow symbols from being accessed inside the same package only.
I’ve spent the last months analyzing how to optimize iOS apps to maximize conversion of in-app purchases. Here are the most important things to look out for: