That's a Q-style lab, not a James-Bond style lab.

Desalination is extremely power hungry. Which means huge amounts of coal, natural gas, petroleum, or other non-renewable energy sources. This could be done with wind or solor but the output of desalination will not be very much, the expense will be huge. So the FIRST step should always be conservation and recycling/re-use.

It is misleading though. Many cattle are raised on grassland and that grass is not irrigated but grows due to rainfall. But the stats will add in that rainfall as part of water consumption of beef. Hay can consume a lot of water but it is a supplemental feed for pasture cattle for winter time use (though dairy cattle it may be the bulk of the feed). This is also part of the problem with the drought: pasture land isn't growing as much grass so then more hay is needed.

Also note that the water isn't lost. Ie, 102,000 gallons of water for one ton of starchy roots, but most of that water is reclaimed in that it evaporates and becomes rainfall somewhere else. Even the water that remains with the vegetables eventually gets returned to the ecosystem. It's really only a problem with a drought.

In some places meat is the only way to turn those grasses and leaves into human food, especially if the climate isn't good enough for regular farming.

If there are people who are upset at all this and think we need a vegan diet to save the planet, then ask them how many gallons of water are needed to raise a human child to adulthood and old age? Are these people following the unscientific advice to drink 8 glasses of water a day and stay hydrated? If cattle take up too much water, then so do lions and gazelles.

I certainly don't work 60 hours a week. I have coworkers who do, but I think this is of their own volition. Possibly they assume that they must work this long or else bad things happen, others are just workaholics. Granted they may be getting more done overall or getting a small amount more compensation, but I am not getting glares from anyone in management by not working on the weekends.

Possibly workers may think that they need to get a set of tasks finished in a day but then they get sidetracked with meetings or unrelated problems, so at the end of the day they discover that the tasks aren't done and put in a few more hours. Whereas I just say that it's not done and I'll get to it tomorrow and go home.

Most engineers or programmers in the Bay Area are paid by the job, not the hours (I'm not counting the IT techies who are hourly or on-call or whatever). Which means you get compensation without filling out hours or being paid by the amount of output you have. Thus they're not subject to the "40 hours a week" because no one ever tells them explicitly how many hours to work; if they can get their assignments done in 20 hours a week versus 60 then that's fine. However if they do get stuff done in 20 hours a week then management will sometimes start adding more projects.

With most good companies you will get some times where there's a lot of work and stress, but then times when it's relatively lax and easy going, with most of the time being in-between. The problems come when every single week is crunch time and that's the sign of a bad company.

Lisp does not fail at resource management. Bad Lisp implementations do that. And sadly, those bad implementations cause people to mistakenly think the language is inherently bulky or inefficient.

The majority of developers will also never need to do anything that involves a lot of thinking. And as time goes on they may wonder why it's getting harder and harder to get a job, or why they're always stuck doing pretty simple business apps.

I see people who do O(n^3) problems quite a lot. They don't necessarily intend that, but there's an O(n) library function that gets called in a loop, and that gets called in a loop, and the programmer never gets around to figuring out why things are so slow. I have seen some people realize why it's slow, but they refuse to fix it because they refuse to write a routine if a library routine does the same thing (I've seen someone argue vehemently that STL's maps were proven to be the most efficient they could ever be, as if I were speaking heresy when suggesting alternatives).

Some people want to box things up into compartments. Sure it's useful to know Roman History, but that's for other people they think. So they learned Java and know nothing else but that, and leave the repeating history thing to politicians. They leave the theory to the mysterious people who write Java frameworks and runtime (possibly they're wizards), they leave the optimization of their programs to the customer who's job it is to buy a faster computer every year.

This isn't just about preparing someone to be a leader; plenty of people are happy being followers. However people do need to be prepared to know when a leader is worth following, ability to point out when a leader is wrong, whether that leader is the POTUS or a CEO or a manager.

Disagree. This theory is MORE important than the particular skills. Because that fad language you learn today may be ignored in 5 years, or 10, or 20. But the theory still works. We have hundreds of thousands of code monkeys who write crappy code but very few who write good code. There is no CS class I've taken that has turned out to be pointless; and I took every one of them except databases and VLSI (and those two are useful also).

Even if some class is pointless as far as skills; the whole point of university is to LEARN and those classes are good at teaching you to learn and forcing your to think. Whereas learning how to use some new framework or language teaches you very little. Teaching you to do a job is not the point of a university education. You can go to a trade school for that, learn how to program at the junior college in half the time. The university is training people for life, for adaptability and versatility, to make someone well rounded instead of just a code monkey.

Attempting to learn the minimum necessary is the same as attempting to be ignorant.

This is IT. You can have a bag full of certificates and not know what a root cert is. These guys aren't the equivalent of bankers, they're the bank tellers.

One problem is that the school's IT "specialists" are not specialists. They're basically going to be inexpensive IT flunkies and one IT admin. You'd have to get up to the level of a school district before they start hiring people more like what you'd expect in a large corporation.

As the earlier story had posters indicate, there are valid reasons for doing this. A root CA is not always about spying. It is likely part of some proxy software they had or some other application. Of course the IT people didn't know about it, this is just a small school where the IT people are installing external software without running it through a lengthy investigation first.

I overcame cancer by keeping the dream alive that one day I would win an olympic gold medal in a sport you've never heard of, in a city I've never heard of. When that dream failed to come true (apparently you need athletic talent) I invented bitcoin instead and used my dentist's name on the paper.

Often the audience gets the slides to read on their own later, as reference. The audience should, in a good presentation, be listening and not reading. I have put up a big list of status codes which I didn't expect everyone to read right there, but I knew that people were going to ask "where can I get a list of these?" (which they actually asked about 2 sides earlier). Elsewhere it was about one slide per new feature, some were a bit complicated but all explained if anyone was listening, but if they weren't listening all the information was there to look at later.

If people weren't spending hours trying to force PowerPoint to draw something correctly, then they'd be forced to do actual productive work instead.