Album

Yep so you know it's bad because Royal blood is pretty thick.

Depends on the docs but if they're written well you're best served by reading them in full. Rftm before looking at best practices and tips.

Problem is a lot of people don't understand how to read a doc. There's a terminology, phraseology, syntax. I have so many instances of people who say they didn't see the answer in the docs and then you look and it's right there. But the human mind tends to discard info it doesn't understand how to process.

If you think you know how the Internet works but haven't read the RFCs you might not know as much as you think you do. Read pretty much every one on ipv6 because the second hand resources are absolutely garbage.

Almost for sure used their own investigators to find out the truth. Then once they discovered the truth would hurt them and there's enough public evidence they're preemptively distancing themselves. As damage control. The question remains if they will self-report or wait for the truth to inevitably come out on it's own. Likely the latter.

Used to be like this. Now I'm like how much can I cram in before 2pm.... Annnnnnd I'm late.

That's not half bad.

Your soul is mine!

Wallet, keys, phone

Unironically probably a decent use of AI

People can also just not install those things. No one is forcing it.

Change logs are kinda hard to do in a CI/CD environment because of the way that development style works.

It's actually pretty challenging in general. Not sure you've ever built a change log before but it's a pretty interesting exercise thats easier said then done. Even open source logs just copy paste the commit log which can be not all that helpful.

If crabs could read there would be no stopping them.

"Forgot my wallet?"