Month

June 2018

1/ There’s a lot of excitement in my timeline about Apple’s new App Store review guideline 3.1.3(b) that allows sales through a developer’s website (thereby avoiding Apple’s 30% cut) for multi-platform apps. A couple thoughts:

Posted on June 5, 2018

Fresh bread!

Posted on June 4, 2018

A little light reading for next week’s beach vacation in the Outer Banks.

Posted on June 4, 2018

“Software Development and GDPR” – This is a really nice commentary from @oisin on the vagarities in GDPR, and how to deal with them as software developers. http://www.oisin.blog/2018/06/03/programming-and-gdpr.html

Posted on June 3, 2018

If simply flagging data as “not to be used” is sufficient for hard drives under GDPR, would the same strategy be sufficient for databases? Because the ability to add a “deleted=1” flag to a database entry (rather than actually removing the data) would make GDPR a lot more usable.

Posted on June 2, 2018

Interesting question from @ianlandsman on Bootstrapped.fm re: GDPR & right to be forgotten: If data is still on a hard drive, has it really been deleted? Because that’s how hard drives work. Data isn’t overwritten on delete. The space it takes up is just marked as available.

Posted on June 2, 2018

One of the”quirks” of Chase Ink credit cards is that a transaction posts to the website about 24 to 48 hours after it’s reflected in your balance. As a result, it’s basically impossible to reconcile your account. Who would design a financial website like this? It makes no sense.