Bill's Dev Diary @billsdevdiary

Mulling over changes to make OTA app dataset updates more efficient, tho update strat may change. Trying to avoid premature optimization.

Have been taking a break since submitting the app. Taking advantage of review time to reorganize / Snowify dev boxen and source code.

Super slammed in the final stretch. If Core Data had a logo as cool as LLVM's, I'd be considering it about now.

Slammed in a bunch of nice animations as a user flow got changed up. Have to push back on more reqs until fundamentals are more solid.

One week to go. Still a ton of UI tweaking to do. Performance is pretty good now, though, last thanks to a couple convenient indexes.

Now have a quick build configuration that'll prefetch and build a clean local store for the app. Ready to play with performance ideas.

Now to adjust when fetches are performed, etc, to improve perceived performance. Feels unacceptably slow right now.

After a bunch of server ups-and-downs, the app's now working with 30k+ locally persisted objects. Slowly, but it's working.

New OTA data update routine magically came together! Was dreading that first run; took most of the day to get it to a testable state.Stoked.

Tomorrow's the big rock of updating the app with 10x the records and seeing how it responds; also,new approach to dl'ing dataset updates OTA

Server's being updated with app state nicely now, though needs a little polish and to re-send failed updates on next launch.

Hrm. Not experienced enough with Core Data to flirt with making this managed object a singleton. Making the safe play with deadline looming.

Filtering working like a charm, filteredArrayUsingPredicate: is my brandy after a snowstorm.

Remind me to check that I'm listening to notifications from the right object before going off on a wild-goose chase again, OK?

Getting back up to speed. Put together a UI for filtering our data set last night, now to play with some NSPredicates.

No hacking for the last couple days after a little med procedure in the ol' neck. Hoping the enforced downtime brings some fresh insights.

Sorry new followers, just now catching up on follow-backs from my main account, @billkunz !

Don't forget to set the locale for NSDecimalNumber's numberFromString:locale: if you're going to display 'em or take 'em from user input!

Cleared out a crasher where my main NSManagedObjectContext was being reset twice in succession w/memory warning. Bah.

Slick design rolled in and it looks pretty hot. Have to step away from it for a little while to try to catch any little nits that crept in.