Have an immutable filesystem, where "deletes" are recoverable by going back in time. At least until you do a scheduled "actual delete" that will reclaim disk space.
Practically speaking, if you're quick an 'rm' isn't totally destructive even without backups. There's a good chance your data is still there on the disk, it's just not associated with anything so it could be overridden at any point. Best to mount the disk read only and crawl through the raw bits to find your lost data (I recovered a week's worth of code this way several years ago).
If we're going to try to come up with a system, mine is simply (borrowed[1]): I like beef and broccoli, mind your business. I readily admit this doesn't cover every corner case, but I don't think there can be a satisfactory system that does. Many things have to be determined by context and taste, and usually aren't even worth thinking about if you're not in a position of power and responsibility over the lives of others.
What's so bad about prefacing the meeting with "Sorry guys I'm expecting a call at some point today so if my phone goes off I'll need to leave to answer it"? Some people must surely be expecting calls from someone of an unknown number every day individually, but I would be surprised if it was a large number of people.
Education on the individual level just doesn't work. People are too dumb. (I had the pleasure of rereading this recently: http://www.overcomingbias.com/2009/07/stupider-than-you-real...) Those that aren't too dumb lack personal responsibility, which is a separate problem I fully agree is pretty big, so more education might fix that, but that's sort of something you can't learn from a book, and arguably the game of chicken at teaching responsibility by making it illegal to discharge student loans in bankruptcy has just made things worse.
The solutions I think have the best shot are those that involve authoritarian decrees one way or another (that is, going full free-market or going full nationalized colleges), but that requires a government with an actual interest in governing.
Or if students had the option to discharge their debt in bankruptcy at all, how many would do it. I suspect enough that we'd have something resembling the last debt crisis on our hands, but depending on how that gets handled it might encourage lenders to be a bit more careful with who they lend to and how much they're willing to lend in the first place which may then encourage schools to lower costs.
I went to college for a number of reasons despite already being skeptical of the "party line" everyone was telling me about how important it was to go to college, but ultimately I was able to swallow the estimated $100k price tag at the place I wanted to go the most (which was small, private, and out of state) because I made the calculations that let me be confident that if I made it to the end it shouldn't be too difficult to get even an entry level job in some field of tech I already had experience in (my degree was computer engineering) at $60k/yr which wouldn't be too bad for paying off that debt. Things more or less worked out, I too don't use any of my degree knowledge on the job and the thing that gets me the most recruiter spam is my broad experience working for peanuts on/off at a local startup while I was still in school. Certainly the degree would have been cheaper by going to the state university, or a community college first, but even those figures are starting to rise and when you can't get any job $30k of interest-accumulating debt probably feels about as back-breaking as $100k. I don't know if I would go back and take the safer, cheaper path. I think I did alright given my information at the time, so I don't put all the blame on the system -- too many college students just don't do the steps of calculating the full program cost (including any loans for housing), the desirability of employees with this particular degree over a degree in general, and then figuring out a plan to actually pay back what they borrow for the degree.
It's a lot easier for people to see this argument with basic income than with minimum wage, but the signaling on property owners ends up being the same whether you know for certain all your tenants now have an extra $x in funds or just some of them might now be getting a raise to the new minimum wage. From the property manager perspective, suddenly they're getting more demand on units than they were previously, so they balance that by increasing rents. An increased minimum wage can play a part in that rise in demand even if no single person can afford an apartment on their own at minimum wage. For instance perhaps there's a group of 4 people cramped in one apartment, but now with all of them getting more money, they can afford to split off into two groups of 2. Until the landlord raises rents, anyway, because they aren't enough units for everyone to do that and building new units takes time.
King County property taxes have been steadily going up, that's a bigger factor than minimum wage. Even in the sprawl around Seattle, prices have gone up, but I hope they'll see a regression since the commuting situation is if anything worse than it was even just a few years ago especially on the Eastside with the 405 toll lanes.
If it actually happened, that's both pretty hilarious and sad for all parties involved. The unintentional fallout has been much more amusing to witness than the actual gimmick of putting a Minion in everyone's email.
I can't get on board the tear train of "victimized by technology, technology maker should make amends!" when the impact of victimization is so small, even the "lost my job because technology maker and especially my boss are retarded" is pretty low-impact. I generally have the attitude of "Sucks, but get on with life" to a lot of things, though.
Even being inherently relative, you still need to determine the underlying values with some metric (like implicit type conversions, or max deadlift). If you tell me someone's max deadlift is twice their bodyweight, that tells me they're strong, even if it doesn't tell me their relative strength compared to say Sigmarsson. If someone says "Language X generally forces you to be explicit with your type conversions" that tells me it's strongly typed. Is it more strongly typed than language Y? That depends on explicitness exceptions -- e.g. Java does implicit autoboxing and toString()ing when you're doing string concatenation, Go effectively type aliases primitives so that e.g. net.IP can implicitly convert to []byte, Python complains when you don't explicitly call str() on things but converts numbers pretty freely (like auto-converting to a bignum, whereas other languages might throw an exception or automatically and silently wrap-around to a much smaller number than expected).
Seems odd to lump Python (which is pretty strongly typed) with Ruby and JavaScript (JS especially not being strong). Edit: Actually this whole thread makes it seem like we all have our own different definitions on what makes something "strongly typed" (or just confusion with strong and static). For myself, a language's type system's relative strength is all about how it handles (or doesn't handle) implicit type conversions.
The simple theory I use for explaining Perl preference is that it correlates to your preference and tolerance of postmodernism in general. http://www.wall.org/~larry/pm.html is a good elaboration on the postmodernism of Perl, I think.
Yes, but that doesn't mean you can't benchmark them anyway. And I think you could probably find some meaningful comparison. Certainly it would be more useful than the Druid whitepaper's benchmarks against MySQL. (I used to work on a DB project, we too had a benchmark against MySQL even though our DB was OLAP-focused.)
Another option (though last time I tried it, it didn't work..) is something like libtrash: http://pages.stern.nyu.edu/~marriaga/software/libtrash/ Deletes become moves and you can really delete when you like.
Practically speaking, if you're quick an 'rm' isn't totally destructive even without backups. There's a good chance your data is still there on the disk, it's just not associated with anything so it could be overridden at any point. Best to mount the disk read only and crawl through the raw bits to find your lost data (I recovered a week's worth of code this way several years ago).