Re: In order to stop another country from destroying you ....
It worked for the Russians and the Soviets.
452 publicly visible posts • joined 30 Dec 2014
Which is ridicoulously low. If you want more than that you need commercial insurance (which doubtless will go up now). ALso any insurance companies on the line to cover other accounts will probably start selling stocks and bonds to cover the expense.
Other limitations may apply.
First off +1 to @sudo-su and @Pascal Monett
A big chunk of the problem is most programmers are functionally illiterate when it comes database models. There is is trend to get rid of DBAs. In one case I commented on they got rid of the DBA and replaced them with a programmer on the team. Basically ending up with a programmer with possibly no background and/or interest in data who is actually and embedded DBA and bound to make all the same old mistakes and re-invent the wheel time after time.
Basically we have Graph Databases due to marketing. "Hey look at are new shiney shiney graph databases! Pay no mind to what the hot new shiney shiney graph databases were in the 70s".
Codd saw the problems with graph and hierarchical databases and defined the Relational Model that solved those problems and more. He also created the Mathematics to back it up.
I've worked with both Graph and (at least quasi) Relational Database models. Relational (at least quasi) wins hands down. But hey, if you want to waste your money on a Graph Database where things take longer to build than they should and they often require constant maintenance, then I'm happy to take your coin.
A Graph DB Model is a subset of a Relational DB Model because a graph is a subset of a relation.
Here's what I see graph DB are liked by those who:
1) Don't know databases
2) Don't understand graph DBs
and/or
3) Don't understand the relational model. Related: that SQL is a scripting interface to a DB API and NOT a way of modeling data.
Yes I sound like a cranky old codger. In fact I am a cranky old codger who is tired of seeing the same mistakes made over and over. Now get off of my lawn!
and possibly puts the procedure in context and what to do if something starts to go wrong. E.g. faced with a problem you basic Windows user will want to warm start the machine. This could be a bad thing. Instead you get a warning "DO NOT REBOOT MACHINE!" a trouble shooting procedure to follow and who to call if said troubleshooting fails.
Part of their play was hiring away talent from potential competitors. the basically gave the talent toy projects to play with to keep them happy while putting them under long term contracts to keep them away from competitors or starting up a company which might compete.
I worked in a refinery and we did "lock out tag out". You had a brass name tag that fit on a pad lock. You used said pad lock to loch machinery in the "off" position. Thereby preventing an intense emotional events in the form of electrocutions or being sucked into large moving machinery. So if working on a system, lock it out because Mr. Murphy.
Let's race headlong for mediocrity in a downward death spiral like all those other tech companies (though it could be argued that Google+Alphabet is a marketing company that happens to produce tech as a side effect).
Take a one size fits all approach and let it become a McCompany with McJobs run by McManagers.