The last one seems like it could also be problematic, how do you distinguish the 1960s decade from the literal year 196. In this case it’s kind of obvious since photography wasn’t very popular in the year 196.
Lots of people have a hard time just freebasing in an abstract conversation about how they work and storytelling “My Journey” type stuff but work just fine in an actual team setting with concrete products, features, and problems to think and talk about.
I hope you count "stimulating our minds for either learning or imaginative purposes" as one of those outcomes because if you only count "work produced and kpis met" as an outcome then that sounds pretty bleak.
I believe the concern is if your primary key in the database is a serial number it might be exposed to users unless you do extra work to hide that ID from any external APIs and if there are any flaws in your authorization checks it can allow enumeration attacks exposing private or semi-private info. With UUIDs being virtually unguessable that makes it less of a concern.
Thanks for posting. The rest of the blog is also short and sweet, I’m struggling a bit with self worth and self criticism so I found it very touching and relatable.
It’s kind of interesting how I’ve come to expect blog posts to be much longer since microblogging pretty much exists exclusively on social media.
In my memory of Plex on my Apple TV device it was off by default and hidden in an advanced menu or something. Not impossible by any means, just annoying.