15,182 karma · joined February 19, 2011
One is co-production of other materials -- wool is another desirable material.
Another is optimizing land use. Some land isn't suitable for row crop agriculture, but can sustain grazing. There's also land we're irrigating for row crop agriculture right now from aquifers we really shouldn't be; converting it back to grassland and grazing on it would let us recapture some of the lost calories.
Then there's un-optimizing the food chain. From a food-per-acre standpoint we should be primarily subsisting on soy and whichever of corn, potatoes or rice grows best in the local soy & climate. Even if we are going all in on minimizing land usage, however, we don't want to produce exactly as much food as we need, because crops fail and famines are bad. You can aim to overproduce a little year to year and maintain a surplus of storage to cover the bad years, but you can't just cover the average bad year. You need to cover the worst years possible happening several years in a row, you need to be covering once-in-millennia bad luck. So you need to overproduce enough that you don't expect some of it to ever be consumed by humans.
So you need something to do with the extra corn you produce, besides feed it to people, that you can rapidly cut back on in case if crop failures to return food back to the supply. One option is ethanol, and another is livestock -- feed your surplus grains to livestock, and then eat them instead. If you have crop failures, you cull the herds, which frees up their feed stocks for human consumption, as well as adding the extra meat calories to the supply. (And this even happens somewhat automatically with market forces -- farmers are always arbitraging grain prices against meat prices, and a spike in grain prices will lead them to sell off livestock as they become less profitable, which will in turn depress meat prices further.)
I'm not saying someone won't convince everyone on board that a silver future for their Nth-great-grandchildren worth derailing the golden future of their 10Nth-great-grandchildren (especially if it looks like the generation ship won't last 10N more generations), but from my POV sitting on a couch that isn't on a generation ship (well, not something traditionally defined as a generation ship), it doesn't feel like something you'd get everyone all fired up over.
Sure, a thousand generations will live and die along the way, but once we get over there, you've got stars every 0.1 ly or so, and with very plausible future tech, you could navigate between them in a few years. You could set up a proper starfaring, interplanetary civilization, with tradeships either going back and forth between two neighboring systems, or winding on long, never-repeating routes, visiting a dozen or so star systems in a human life.
(Most globular clusters appear to be old and metal-poor, and we haven't found a lot of planets there, and this only works if you find a globular cluster where ~every star can support a colony.)
First, you have the "our core libraries/dependencies were written when it was 'C with Classes' and we're going to keep using that style for consistency/laziness/because it's well-tested", and then you have the "C++ is ugly/full of segfaults/hard, I'm going to use <new language> which solves all these problems".
You have to pass those two filters before you get to people who are interested in writing good, modern C++.
Were you satisfied with the paper?
Having read the paper, do you understand "what you missed" in those 3000 hours?
One piece of trivia that's stuck with me is that stamps were used as a substitute for coins when the latter were in short supply during the Civil War because of metal-hoarding. A 1-cent stamp was basically a paper penny, backed by the value of just being able to stick it on a letter.
Why an artificial intelligence would want to take vengeance upon its creators is left as an exercise for the reader.
Which is like, not as weird as most AI company headlines, to be honest?
[0] Everyone gets hacked, but not everyone has all of their most secure data exfiltrated.
The other downside of nepotism -- besides the risk that Joe did a shit job and won't admit it or maybe can't evaluate his kid objectively -- is that even if the kid is the bee's knees, a great hire, it's not really fair -- there's almost certainly other candidates who are just as good and trustworthy as Joe's kid but they can't compete with either Joe's kid. It doesn't really matter what sort of references or credentials a candidate can show you if you can serve as a reference for the other candidate. You can't really run a meritocracy like that.
So if you have old two-prong outlets in your house from back when, those are allowed.
If you replace them with a three-pronged outlet which is ungrounded, that breaks code.
If the three-pronged outlet is a GFCI outlet labeled with NO ELECTRICAL GROUND, that is allowed.
I'm curious how this looks with various ways of normalizing for amount driven; is that no-accident crowd the quartile of drivers who don't drive very much? The biggest factor in being in the opposite group (the 10% of drivers with 50% of accidents) is "drive all the time, commercially or otherwise".