herdrick

More generally, trust your gut, especially when people start talking about Methodologies. Your instincts are good.

They didn't give conditional probabilities but of course we can, and should, use what we know about the world to make guesses at P(E|'likes math'), or at least whether that's greater than P(L|'likes math'). It surely is and you can do something similar with carpentry and an apolitical nature.

It's true that even with the assumptions I've given above you can't come up with a precise answer - none of the choices are any good - you can certainly say that "...the correct response being precisely 30 percent" is thoroughly wrong.

That's amazing to me. I thought such things were never done in software anymore because: why not leave the company and do the same thing in your own startup? Same hard work, high risk, etc, but with giant upside. Was it because of something wrong with Seattle's startup culture?

I only mention this because I think a lot of us here want very much to be like Steve. We need to work to avoid imitating the wrong things.

"WGU’s answer to the status quo is to offer a degree that is based on competency rather than time. By gathering information from employers, industry experts, and academics, Western Governors formulates a detailed, institution- wide sense of what every graduate of a given degree program needs to know. Then they work backward from there, defining what every student who has taken a given course needs to know. As they go, they design assessments—tests—of all those competencies. “Essentially,” says Kevin Kinser, a professor of education at the State University of New York at Albany, “they’re creating a bar exam for each point along the way that leads to a degree.”"

Is this worse than the sort of thing that goes on in the early days of most startups, including our most revered? People around here have a lot of respect for pg, rtm, tlb and their startup Viaweb - go back to "Founders at Work" and read how they got computer time needed to get the startup going. That kind of thing is practically universal in startups. The good ones, anyway.

So Aaron appears to have cut some corners in getting an interesting project off the ground. Slap him on the wrist.

EDIT: In fact, I think that whole section should say the opposite: "2. Refusing to quit with unexercised options"

This is the traditional realtime processing use case: process messages and update a variety of databases.

Question: I typically think of real-time as a need for user-facing things, i.e. handling a user's requests before he gets bored and goes away. Is Storm set up for that? Or is it mostly meant to update a database with results rather than return them to a waiting process?

It's funny, WWU CS has a repuation for being a very pro-Microsoft department. Not sure what's really going on here.