Swift and Go. Love 'em both. They make me mad in completely different ways. Infosec as required. https://xitter.cf/t.co/Tx31kqZCRI
Raleigh, NC
Joined May 2009
- Tweets18.2K
- Following445
- Followers6.9K
- Likes12.4K
Pinned Tweet
I'm not particularly leaving Twitter, but I am spending a lot less time here. Most of my posts are now on mastodon.social/@cocoaphony, and that's where I spend more of my time reading. I'll post to Twitter for things that need more reach, and I still look at Twitter every day or two.
A short anecdote on getting answers on the modern internet: cocoaphony.micro.blog/2023/0…
A Reminder About NSRange and String: cocoaphony.micro.blog/2023/0…
Big-O matters, but it's often memory that's killing your performance.: cocoaphony.micro.blog/2022/1…
Life comes at you fast.
In a few weeks, my "I'm bored" muscle memory has gone from "tw\n" to "mas\n". (after "sta\n")
I think this wake is premature. Things can shamble on a long time (livejournal). But still, Mastodon has already replaced this for me. Took 2-3 weeks.
Any custom Instruments experts out there? Maybe this is just a limitation in Instruments to keep it faster?
stackoverflow.com/questions/…
I've never had a response from Apple so fast & helpful through dev forums (not counting Swift forums). Even though the answer is "this isn't possible, please open a FB," that's totally fine, and for once in a long time, I was happy to open the FB. developer.apple.com/forums/t…
Rob Napier - @[email protected] retweeted
Rob Napier - @[email protected] retweeted
About Friday at Twitter HQ - I didn’t do enough to confirm and I regret the mistake
Is there really no written usage documentation for RegexBuilder? I see one small example in the docs. But I can't find anything else. (That said, @k_katsumi's swiftregex.com is brilliant and helped me a ton figuring things out.)
Spent today chasing this one down. The error message is a lie. The solution is a little ugly, but not difficult and should be quite robust.
cocoaphony.micro.blog/2022/1…
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Solving "Required kernel recording resources are in use by another document" in Instruments.: cocoaphony.micro.blog/2022/1…
Rob Napier - @[email protected] retweeted
I always find these types of discussions interesting. Optimization is hard and I keep finding examples where poor performance has nothing to do with multi-threading or anything other than they choose to repeatedly ask the same expensive question
Rob Napier - @[email protected] retweeted
How to write a great Stack Overflow question dataschool.io/how-to-ask-for…
May I remind us all again to first optimize on a single core, and *then* worry about making things parallel (if that's even needed). It's harder than it sounds to make parallel algorithms fast.
Optimizing the parallel code is forcing me to think deeply about Swift implementation details. Conversely, optimizing the sequential code has mostly been "Run Instruments. Where is my code spending its time? Rewrite that little piece. Repeat."