I was sitting in the family room. Big slam sound. I go out and check the garage and one of the springs had broke.
It is really not a big deal to switch them out.
My take away is that it's to dangerous to do.
I was sitting in the family room. Big slam sound. I go out and check the garage and one of the springs had broke.
It is really not a big deal to switch them out.
My take away is that it's to dangerous to do.
Any time I am doing something that could violate some logical constraint, I am probably trying to fix something that is already fucked. The safety nannies simply add insult to injury at this stage. I will delete broken rows in whatever order I please.
If constraint violations are adding value to your solution, you probably have a far more severe problem repeatedly slamming into the wall somewhere.
Having to write code that can handle foreign key violations because the DB doesn't check it is a major pain. (we use Cassandra for example, so there is a "foreign key" usually from a PG row to a Cassandra row, obviously that can't be enforced on DB level so application code has to do the work)
As for deleting/updating data, FKs can be a bit annoying, but postgresql for example has two (possibly more) options.
1) The (possibly dangerous) cascade delete, which will traverse the FKs basically for you and deletes them 2) The check FKs (and other constraints) on commit. I.e. instead of checking every delete/update statement causes FKs violations, it'll check at the end, after having done all the delete/update statements if there are any FK violations. (or update statements). Called deferrable constraints.
And that's why I don't get how people expect directors/managers to be infallible.
Taking responsibility isn't about walking away from the job, but learning from it and making it right.
Whether that is done well in this case, I don't know, but that wasn't your point. As far as I can tell they got pretty decent severance packages.
A thermonuclear test yielded much, much higher energy, due to unexpected lithium 7 reactions.
- they either require space (forests or whatever)
- are hard to produce in sufficient numbers (materials, production capabilities)
- are expensive to run (like energy input, maintenance), in particular don't generate new red balls while removing them.
- disposal cost (where the machine becomes the carbon, like trees, cutting them down and doing something with that)
Once we got it out, on a "pile of carbon", the problem becomes much easier.
Who reviews "Bricks" of all kinds including Lego. He consistently is annoyed by how expensive Lego is compared to everything else, with usual worse quality (in terms of design, fun to assemble, etc). If you can bear google translate or even speak German, he may be worth listening to.
Anyway, got sucked into that and got my first "brick" set since around 25 years ago and it felt like Lego (as far as I could remember). Instructions, presentation, the stones, everything.
I believe "Cobi" and "Bluebrixx" are often mentioned as good, affordable (seems about half price for similar set) and lego compatible. From what I understand the patent for the particular form factor of the bricks ran out, which is why there are a bunch of alternative now.
I got that one: https://cobitoys.de/small-army-ww2/panzer-und-fahrzeuge/panz...
I live in the UK, think I got it via amazon, so maybe more difficult for you Americans.
Either US company get's the data from the Italian one, making the Italian operation illegal in Italy
Or
The US company doesn't get the data from the Italian one (despite ownership), making the US company illegal in the US.
I don't think anyone is under the illusion that the latter option is chosen when push comes to shove.
Unless the stuff is on the surface of the meteorite it's probably fine.
It's generally a good idea to drop vowels for this reason.
We never had a similar issue with our random numbers/letters/reset passwords or anything like that which don't have any kind of "dont return profanity" protections. Though I agree, someone getting a randomly generated customer portal url or something containing fuck or similar would look bad. Our cloudfront or something (or was it main public facing s3 bucket? can't remember) starts with "gay" and was never picked up on.