“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
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.
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.
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.
A friend of a family member called me for some free advice about his idea for a mobile app, and to see if I could recommend a developer. But first he wanted me to sign an NDA.
Me: “Sorry I don’t sign non-disclosure agreements.”
