Basically, the strategy is "death by a thousand paper cuts." There may be legit cases for it, but in the end, it's a wrong solution. It could easily explode to be abused for minor complaints where a real class action lawsuit would be more proper. There should be a cost to a frivolous lawsuit. This seems to eliminate it.
This is going to be a social experiment on an unprecedented scale. And it will be impossible to roll back, after we learn all the unintended consequences.
Yes, you're right. It really doesn't take a genius to make a sourdough. But you're misunderstanding the tech people. They will take tying shoelaces to the genius level. Same with baking bread. And it's a lot of fun for a lot of us.
For those of us working in tech, it can be extremely satisfying to bake your own bread. I did that a few years ago, starting from scratch, making my own sourdough starter, and baking daily. It's rediscovering what a typical family did centuries ago. Your starter becomes a pet.
I had to stop it due to a lot of travel, but I still have a packet of my starter vacuum sealed and frozen.
Maybe I should try again. Travel certainly won't be an issue for a while.
This should also allow to monitor for mutations of the Covid 19, whereas it would be impractical to do at an individual level. It would give an early warning signal.
Obviously, there's the iconic K&R, which some people don't like for its terseness. I loved it - pure and to the point. However, the second book that made a huge impact on me was "Reusable Data Structures For C" by Roger Sessions.
If you internalize these two books you'll be a highly competent C programmer.
https://www.amazon.com/Reusable-Data-Structures-Prentice-hal...
I don't know if I can give justice to it but there are scenes, like the pub owner explaining that he had to remove the portrait of the emperor, because the flies were crapping on it. There's just something that's missing in the translation.
Many jokes rely on language and cultural references. This book is like that.
This is a fantastic book, unfortunately, I haven't been able to find a good English translation. I've read it in Polish, which is close enough to Czech to stay much closer to the original. The English translation loses a lot of the cultural character.
I once had a dream of being in a ballroom of a fancy hotel, and the smell was overpowering. I was thinking that there must have been a murder and they've bleached the carpet.
Turns out, my wife was already taking a shower and used a new brand of shampoo. I couldn't stand the smell of it.
Somehow, contemporaneous reality entered my dream, rather than a memory of a past event.
In the mid 90s I wrote and supported a C++ program for moving around and processing data in a semiconductor factory. It ran on Windows and two different flavors of Unix. Half of my time was spent recompiling/relinking and trying to keep up with the upgrades of the few libraries I've used.
When Java came out it was so liberating - I'd write a new version of the software on my laptop and ship an update to a client with HP Unix and it would run without a hitch.
I doubt that there's still a lot of use of C++ for entire applications. I suspect it's mostly used in performance critical components.
I don't underestimate that, but I'm amazed how many crimes still go unsolved with criminals leaving their digital crumbs. I highly doubt that many criminals are smart enough to simply leave the phone behind when committing the crime.
Interestingly, deleting the vim executable won't exit, because Unix has the "funny" habit of keeping a file handle alive as long as it's referenced by a process.
Really cool way to mess with some noobs.
I once found a system where a third party vendor installed vim as root with suid permissions.
I've had a few days of fun before I finally decided to clue the sysadmin about it.
Granted, I have never worked with a database the size of Github, so I've never had to deal with sharding issues. But, even though foreign keys can be a PITA in some situations, I prefer the DBMS to do it for me than rely on the application. Foreign keys have always kept my back. I've been burned a few times when they weren't used.
While security is being mentioned as one of the strengths, and I certainly agree with that, there was a version of VMS in the late 80s which wouldn't let you create a password if another account already used it. In a small department it wouldn't take more than 15 minutes to hack into someone's account.
I have to have a mental model before I touch the keyboard. It's probably wrong on the first iteration, but without a mental model how would I know if the code is doing what it's supposed to?
I find it ironic that someone so concerned about hidden cameras is advocating hack attacks on the host's network.
I run an Airbnb, no cameras, not even on the door. The only sensor I have is on the Nest thermostat to automatically turn off heating when no one is present.
I expect the courtesy of my network not being hacked into by some wannabe hacker.
Kudos to Mazda for saying no to this insanity. Not only is it unsafe, it's a horrible user interface. I'm not able to drive and hold my outstretched arm steady enough to select an item with a finger. For next car purchase I'll definitely test drive a Mazda.
In my consulting career, I've seen major organizations track data in Excel, updating each month by creating a new set of columns. An absolute nightmare to handle. Of course every month the structure changed slightly, to make it more fun.
I've also seen values stored as an #rgb only - no actual value in a cell.