6 Comments

In the Cookie diagram I agree their original purpose was benign and they can be helpful, but you're missing the nasty side effects where Bob gets 472 other store cards in the same transaction, and all those store cards report where Bob has spent money to their own coffee shops so those shops can advertise the right coffee, shoes and political party to Bob.

Expand full comment

Hmmm. It would be ah… ‘fun’ to show that in a third panel. Add some advice about cookie blocking… 😏

Expand full comment
Feb 4·edited Feb 4

In Cookie diagram, I guess flow 4 should be a Response

Expand full comment

Good coding principles should always include GITCs, particularly around change management. Even though approvals and testing scenarios is not the most exciting, it is an important part for these roles in companies. Really nice information you are sharing.

Expand full comment

g g y yy yyyy

Expand full comment

Wow, this is like a tech carnival! Disney Hotstar capturing a billion emojis, a coding principles extravaganza, a network security cheatsheet (because who doesn't need a good cheat now and then?), unraveling the VPN mystery, and a cookie class – wait, is that a snack break?

ScyllaDB Summit sounds like the Woodstock of tech talks! Bo Ingram's keynote about everything being great until the database is down – talk about drama in the server room! Lessons from Discord's outage? Sign me up! Also, a book bonus? Just when I thought the tech world couldn't get more thrilling.

"Everything should be made as simple as possible, but not simpler" – and these coding principles get it. Following PEP 8, a SOLID foundation, making code as robust as a tank, and promoting documentation that's more than just a cryptic hieroglyph – it's like the Avengers of coding standards

Expand full comment