I've been to college myself, and I bet MIT would be around 1:1 too. The thing is, a lot of the teaching isn't done by faculty, it's done by graduate students. This includes recitations, answering questions one-on-one, and grading papers.

And there are a ton of administrators too, and they aren't sitting around on their hands doing nothing. They're doing stuff like administering grants and supervising the IT and physical plant people necessary to keep the faculty's lab research running.

The biggest time waster for MIT faculty, as far as I can tell, are other faculty.

No. Some wars are about controlling geopolitically strategic territory... and they start out rather like this as well.

Most folks today don't remember the Cold War or Alfred Thayer Mahan's sea power theories, but you can bet the old men on the Politburo Standing Committee do.

Of course you could replace the particles mentioned in the article with names from my kids' Pokemon decks and it would be just as meaningful to me, but I'm still taking it. Good news is hard to come by.

I keep hearing this, but perhaps it depends on your locality. Looking at the first hundred entries in our local school staff directory, I get:

71 teachers
8 secretaries *
5 special needs professionals (4 speech pathologists +1 occupational therapist)
5 nurses
4 principals*
2 guidance counselors
1 police officer
1 payroll clerk *
1 information technologist *
1 Librarian
1 assistant superintendent *

* administrative staff

So going by this sample, 15% of the school department employees are "administrators" of some sort, although most of these are secretaries who handle a lot of things that teachers and more highly paid administrators would otherwise have to. But I hear people in my town make claims like the one above, even though they could just look in the school department directory and see for themselves this isn't even close to true. They believe this, not because it's factual, but because it's "truthy".

It's like when my town passed a tax increase to pay to replace the crumbling middle school. There was an anti-tax group in town that claimed we shouldn't give the school department any more money because they kept the school budget "secret". It just wasn't true. You can go on the town website and see the budget. That's how I know that at the high school teachers account for 79% of the salaries, and that system-wide administration (including superintendent, office staff and system-wide IT support) accounts for about 6% of total salaries. When we voted on the tax increase referendum I actually saw a parent try to hand a printout of the budget to an anti-tax protester holding a "no secret budgets!" sign. The protester literally recoiled, like she'd been offered a ripe piece of roadkill.

Are there schools or school departments out there that literally have more administrators than teachers? I don't know; maybe there are. My point is we shouldn't believe this about some school or school system simply because it sounds true to us. We should check. And if the answer is "yes", then you should do something about it.

When Obama first proposed Obamacare, he didn't jump in with specifics; he just laid out some high level guidelines and let the Democratically controlled Congress hash out the details. This was politically costly, because in the absence of specifics all kinds of claims were made about what was allegedly in the program, like "death panels". The house ended up passing something that looked like the plan Heritage Foundation put together for Bob Dole in the 90s. This was essentially the least they could do that met Obama's specifications for health care reform, and the long period over which it was impossible to defend because it had no concrete form cost Democrats control of the House.

This plan looks an awful lot like that. Broad goals, but implementation details kicked down the road and downstairs (in this case to the states). The one specific detail that's being talked about is a 30% reduction in emissions from coal in 26 years -- and even that's not very specific. The total CO2 emissions associated with mining, transporting and burning coal is at present about twice that of natural gas. It's possible that coal will be mined at even a higher rate than today if the industry develops more efficient ways to use it. Twenty-six years is a long time in technology.

In any case it's kind of a no-brainer that you can't allow coal emissions to grow in proportion to how the country's economy will grow in 30 years; not if you want to reduce pollution. It's the dirtiest fuel we use across the board, not just in terms of CO2.

But however you slice it, this is a very abstract plan that won't be translated into any kind of concrete action until long after Obama is out of office, if ever. The only thing that's close to certain is that it'll create a lot of political turmoil.

What we need to know about is the existence or non-existence of unfair comparisons, i.e., problems that favor the putatively "quantum" computer.

Since I don't expect a quantum computer to be faster at everything, then finding a bunch of solutions to problems that aren't any faster on the "quantum computer" doesn't prove anything, even if the problems look like the kind of problems you'd hope would be quantum-computery. There's not much more you can do than point to the absence of evidence when the burden of proof isn't on you.

The burden of proof is on the vendor here, and standard of "proof" is conceptually simple at least: demonstrate that for some task this device offers any practical advantage whatsoever over the best available conventional technology. That could be in absolute performance against the best available tech(e.g. ASICs and supercomputers), in relative performance over similarly priced systems, or in some practical measure other than performance, such as power consumption. Any clearly identifiable and verifiable advantage counts as positive proof the vendor has something worth paying attention to.

Of course even comparable performance by a novel architecture on some class of problems is interesting, because of the huge advantages a mature technology enjoys. Performance of a new design even in the same ballpark as a mature design suggests future improvements might be in the works. But it's only a suggestion.

That would be terrible, if it was actually happening in any place other than your imagination.

With particular emphasis on "whatever". If this doesn't work, you really can't conclude anything because of all the potentially confounding factors. The only thing you *can* conclude is that other fields are more attractive to young women than CS or coding.

In years of commercial software development, I learned a number of important principles for designing new products.

(1) "Everyone wants what I would want" is a bad assumption. Chances are there are lots of people out there like you, but a lot of the untapped market may be people who want something different.

(2) There is an adoption curve for anything new. At the head of the adoption curve are people who want things that are new because they are new. At the tail are the people who don't want anything new until it's become old. In the middle are people who can be persuaded for various reasons to try something new, but only if they see other people using it successfully. Therefore the first thing a new product must be is new. The second thing a new product must be is practical. The last thing a new product must be is relatable in terms of older technology. A product that achieves all three can eventually sell to all three adopter types.

Notice how the bike in question tries to fit this model. The gear whine sound it makes struck me as unnecessarily loud, and the Harley people went on and on about the distinctive sound it makes. That sound is different from the traditional sound of Harley, which gets the attention of the early adopters. That sound is unnecessarily loud, which makes the bike relatable to a long tradition of unnecessarily loud Harleys. In a way the early adopters will be having a very traditional Harley experience of riding by and everyone thinking, "There goes one of those damned Harleys!"

(3) Experience is not the same as understanding. The classic example is the client who knows which websites he likes and dislikes thinking that means he can design a website himself.

What you experience riding a powerful bike is real. It is also artificial -- in the sense that it was deliberately crafted by talented designers, working with a toolbox of ideas that are probably unfamiliar to you unless you're a designer yourself. That doesn't mean they're smarter than you (gosh that's a big mistake for designers to make), it means they're more expert in their field than you are in their field.

There may be other ways of producing the experience you value, or indeed entirely novel experiences that would be equally powerful. They can try to reproduce the traditional bike experience, or they can try to redefine it. Chances are they'll fail either way because both are going to be difficult. Still, nobody can really know for sure until they get you on their new bike.

(4) Care about what users have to say, and listen to them very carefully, but don't believe them. Presuming they haven't contradicted themselves (which they'll do sooner or later), and you build them exactly what they ask for, most of the time they won't like it. I call it the "I know what I don't like when I see it" response. Your job as a designer is to think about what users tell you until you understand at least some of their needs better than they do. Then provide them with something they want without having realized they wanted it.

All of which means when you design something, it has to be just the right mix of surprising and familiar. The only way to know whether you've achieved that with a product like a high performance electric motorcycle is to build a prototype and have lots of typical users ride it. The results are probably going to be a total dud, as you're expecting. Or they may be a revelation. Or they may work for other people, but not for you.

Or... they could politely ask anyone using a cell phone to leave, pointing to the signs they have prominently posted.

Sure, some patrons will be upset, but not as upset as the parent who misses a call from the baby sitter telling them to get to the hospital right away.

Oh, old Gramps here can trump your whole list:

Thoughts millenials (and younger) never, ever, EVER have:

• "Maybe I shouldn't be texting right now..."

Well, I'll have a pint, thank you!

Well, I don't happen to have a settled opinion on what the "right" price for gas would be, so I don't think gas is "too cheap". But I think the price you pay doesn't include all the costs entailed in that gallon of gasoline. So whatever the current price of gas is, whether it is $1/gallon or $5/gallon, the additional costs of producing and using that gallon of gas should be included in the price, and that will increase the price, whether that price happens to be low or high.

So in effect, I think the price of gas should be increased, but I don't think gas is "too cheap".

Tesla's 3rd generation car is supposed to be a mass market vehicle that may disrupt the "automotive order" if Musk manages to build it. The giga battery factory he is looking for a home for is a critical component since it is critical to have enough affordable batteries for a mass market electric car.

Tesla today wont disrupt NADA, but Tesla in a few years very well may, they know it, so they are trying to nip it in the bud.

I wonder if this isn't a function of the high temperature you use welding. At lower temperatures iron alloys can be extruded and of course shaped by forging, neither process which would work with water.

Most people don't realize, but the technology to melt iron didn't exist in most of the world until the early modern era. Only China had furnaces hot enough to reach the melting point of iron. European ironworkers used a "bloomery" furnace in which they roasted ore. Bits of solid but red hot iron would drop to the bottom of the furnace and stick to each other, forming a dirty ball of iron called a "bloom". An ironworker would then reheat the bloom and forge it into an iron billet, a process which also drives out a lot of the impurities in the iron.

The thing is, those little bits of of red hot iron were a lot more like plastic than they were water. I can easily imagine some kind of 3D printer which melts the end a very tin piece of steel wire, and deposits a tiny droplet that immediately cools to a plastic state because it has very little thermal masss. If you think about it, surface tension is actually your friend here. The thing is, I don't see what advantage this would have over laser sintering.