I’m on call for one of our apps this week. The worst part of being on call is the temptation to do other work during off-hours. I’m usually a stickler about this stuff but always having a work phone on me makes Slack that much closer to me.
I started writing up some of my experiences (and to be honest, big struggles) with learning SwiftUI last night. It’s grown to be quite a large post. Would it be better to post it all in one shot, or break it up as a few different posts?
I need to fix Scorebook’s Settings screen to work with Dark Mode in iOS 13. Great, I thought, let’s rebuild it in SwiftUI. That feels like a good candidate for an isolated test, right? Now I want to bind a Toggle to a UserDefault boolean value and my brain is melting.
I’m really happy with how my Xcode project & XcodeGen Talk went at tonight’s @xcoders. There was some great discussion afterwards and it seemed like a lot of people are excited about getting into project generation!
I don’t understand traffic going north from Seattle. It used to be that I could take the 413 northbound at 3:20 and get to Mountlake Terrace for the 3:50 119 to get home. I’ve not been able to get to MLT by 3:50 for the past few weeks now. It’s really frustrating.
It’s amazing to wake up to the first new Tool music in 13 years. I’m really excited (and nervous) for August 30. I don’t know why I always get a little nervous when a band I love releases new music.
Got the new @xcoders podcast edited and ready for publishing in the morning. Look for it tomorrow!
My kingdom for a fast, easy, reliable way to seamlessly get photos from my Sony Alpha 7II to my iCloud Photo library. Having this happen automatically on my iOS devices is amazing and a huge source of friction in my big camera shooting.
It’s an extra awful traffic day going south on I-5. We’ll get to Long Beach someday.
When your 3-year-old sweetly says “I want to play with you”, that’s the moment you know you’re going to work just a little bit later.
Now I can get to work on a Scorebook update to support iOS 13!
It’s here! Scorebook 2 has landed on the App Store. I’m really excited to get this out the door today! taphouse.io/scorebook
Found the issue, got a fix working. Once this build finishes processing I can submit for review!
Argh, found a crash on launch bug with Scorebook 2.0 on fresh installs. Just when I was ready to call it good. Hoping that it’s easy to reproduce and fix.
I just hit an amazing bug playing Apple’s “new” poker game on my iPhone X. I swiped up to get home, came back to the game and found I’d gone all in with 7-8 of hearts. I flopped a flush so it all worked out but dang that could’ve been bad.
I’ve yet to have consistent success with Fastlane’s Snapshot tool to capture screenshots for Scorebook. I keep getting errors with exit code 65. For whatever reason I’m not able to get repeatable successful results.
OH: I miss the Zune.
After getting Scorebook’s Core Data testing foundation put in place I was able to find a bug in one of my data model calculations, write a test to prove it failed, then fix the calculation and get the test passing. There may be something to this testing thing after all.
Trying to do the right thing and add some unit tests to the data layer of Scorebook. Except now I’m realizing that I need to do a bunch of updates to how my Core Data stack is set up, and wanting to start using NSPersistentContainer to boot. I hope this doesn’t get out of hand.