Me: "hey are we sure this code is correct and still necessary?"
Other developer: "claude says yes"
Cool. I fucking hate it here.
indie dev • iOS & macOS • freelance
📱 apps @hexedbits
all posts are opinions of my former employers.
| Website 🌐 | https://www.jessesquires.com |
| Apps 📱 | https://www.hexedbits.com |
| Hire Me 🧰 | https://www.jessesquires.com/hire-me |
| GitHub 👨💻 | https://github.com/jessesquires |
Me: "hey are we sure this code is correct and still necessary?"
Other developer: "claude says yes"
Cool. I fucking hate it here.
RE: https://mastodon.social/@jsq/116562492331888184
How do I make this go away?
I updated to Sequoia 15.7.7 and now there's this virtual "Update" drive stuck in Finder.
It won't go away, even after multiple reboots.
What the hell?
@mattiem what is the ideal way to do file I/O with NSFileManager and Swift Concurrency?
An actor doesn’t seem correct.
I’ve seen using withCheckedThrowingContinuation wrapping a DispatchQueue. This seems… good? I’m not sure.
How would you approach this? I guess I’m looking for “NSFileManager, but with async/await”
I continue to be baffled at the comical level of complexity that has manifested in Swift.
Did AI design this language?
https://www.massicotte.org/step-by-step-designing-protocols/