Heck, it deletes C:/ ! (Because it gets replaced with /)

My thought as well, but those stones were shaped to match each other, reducing the amount of grout needed. It just goes to show the old ways still work, but you have to commit.

With an extra chapter, describing how to corrupt open source projects

Science is a subdiscipline of philosophy.

Generative AI degenerating skills.

have a dedicated firewall I mean, don’t router firewalls count in this regard? Isn’t that kinda part of their job?

O(n^n)

After a point in your career you either learn the skills and get the experience to understand how to plan projects and end up on those groups writing the definitions, or you remain an IC and just code what was given to you.

If humanity needs insight into anything, surely it is business. Doing market research is doing the Lords work. If only we could structure society in such a way that automatically most of the available money would be directed to market research and marketing, the world would be a better place. I suppose my sarcasm here is obvious. But it's not uncommon to hear people on the right say things like 'but the money needs to be earned first, before it's spent, therefor we shouldn't hinder business in any way.'. As if to say 'we just need to make more room for business people to do their thing, and then we'll be good. It amazes me how people fail to see how 'business' as we know it is such ill-directed human effort. I know, we need to be productive, we need to do good things, I am all in favor of that, but doing whatever makes the most money for a company, isn't the equivalent of what is good.

ACID is really just an arbitrary set of requirements for databases that made sense way back in the day when things were much simpler. ACID starts to hold you back when you want to scale out, because to have consistency you have to wait for your transaction to percolate through all the nodes of your system, and it doesn't allow for things like a replicating node to be temporarily offline or lagging behind. Turns out though that not everything needs to be strictly ACID. For example, there are many cases where it doesn't matter that a reader node has stale data for a second or two. The thing MongoDB does is that instead of being dogmatically ACID all the time it allows you to decide exactly how ACID your transactions and your reads need to be, through the writeConcern and readConcern parameters. If you want it to be completely ACID, you can, but it comes at a cost. Traditionally, ACID is where relational databases shine. Relational databases shine with ACID on single-node systems when they're not trying to solve the scale-out problem that MongoDB is trying to solve, but when they are trying to do that, they actually do much worse. For example: most RDBMS systems have some kind of replication system, where you can replicate your transactions to one or more backup nodes either for failover or to use as a read-only node. Now if you consider that whole system, replicas included, as "the database", none of them are ACID, and I don't know of any RDMBS-es that has mechanisms to automatically recover from a crashed primary without data loss, or that can handle the "split brain" problem.

Source code: https://comicss.art/comics/205/initials.html

Passkeys are an implementation of a public-key cryptography. The service has the public key, you have the private key. The sites don’t give you anything, you give them the public-key which is generated using your private key. https://www.passkeys.com/ explains a lot of it.

I once drove 6 hours (3 to get there and 3 to get back) to turn a printer off and then on again for a customer who refused to touch it at all. I even told him I'd charge him the emergency rate and for a minimum of 8 hours. He was undeterred. It was easy money, but that day trip SUCKED.

Why Yoda switched his major from CS to Jedi Studies