Egg on my face for not checking system requirements before updating. Got approval to update to Sonoma on my work laptop, but we are still stuck using Xcode 14.3, which isn’t supported. Now I get to downgrade. Every app that I use on a daily basis works on Sonoma, except for the one that I need to do my job. 🤦🏼♂️
Loving our GraphQL team right now. Just found out that I can refactor part of our app state and remove some complexity, by merging two network requests into one. 😃
It’s amazing what a week off will do. I was having some issues implementing withCheckedContinuation() and handling cancellations. Read through a forum post one more time this morning and the problem was immediately obvious. I wasn’t calling resume on the continuation when it was canceled and this led to the continuation being leaked.
Now that that refactor is out of the way, I can focus on the main changes for the Drafts action.
The positive side about having my changes overwritten is that it revealed a bug I had overlooked when I was adding everything back.
Forgot that I was editing an action in Drafts on my iPad and made a lot of changes on the Mac. When I opened Drafts on the iPad it overwrote all of the changes that I had made on the Mac. Yay for getting to redo everything. 😔
My plans to tinker on an app idea last week didn’t go as planned. I ended up spending the week getting sucked into a JavaScript rabbit hole to try and clean up a Drafts Action that I created. While it wasn’t what I had started out the week wanting to do, I’m glad that it went this way. I’m happy with how the Action is looking now and will make it easier to maintain going forward.
Nothing fancy to see here, just testing some cross posting fixes for my Drafts action. 🤞🏼
Trying to figure out the best way to introduce changes so that it is backwards compatible, but without making the code a nightmare to maintain, is always a fun part about software development.
It’s always funny to me to look at our app metrics and see what versions are still being used. Noticed today that a version is still being used that was released in 2019. But they are running iOS 16. I guess app updates aren’t as important as iOS updates. 😂
It does make me feel bad knowing that their version is about to break. 😔
Trouble with NSDiffableDataSourceSectionSnapshot
It is definitely a case of the Mondays today. I was thinking that I broke push notifications, only to realize that I was using the device token from the simulator instead of from my device. 🤦🏼♂️
What a way to start a Monday. Could not remember how to pass a type as a function parameter and had to look it up to remind myself to add .Type. How’s your Monday going? 🤦🏼♂️
Slowly but surely I am learning to bend UICollectionViewDiffableDataSource to my will. Still have a lot to learn, but figuring out the best way to structure the data for the snapshots has been my biggest challenge. Not making the section identifier as simple as possible initially was my biggest mistake.
Staring at a newly created project in Xcode is, to me, like a writer staring at a blank piece of paper.
Number of days that I forgot to set translatesAutoresizingMaskIntoConstraints to false? Zero.
🤦🏼♂️
Falling down the rabbit hole of refactoring some code thinking that it can, or should, be cleaned up a bit only to end up back where I started and realizing that this approach is perfectly fine.
I spent an embarrassing amount of time, this morning, trying to figure out why my collection view cells weren’t refreshing when I updated the snapshot. Only to realize that I had added a custom equatable function to the struct that was only checking the id value, which doesn’t change. 🤦🏼♂️
I am not sure who needs to hear this. At 42, I still deal with imposter syndrome. Asking for help can, sometimes, be such a challenge. There is no silver bullet to get rid of this. Just keep rocking you and know that you are not an imposter, and you deserve to be doing what you are doing. 😊