tdenkinger

This was not my experience. I did not get an offer after being flown out and spending the day interviewing. I did not do well in the whiteboard coding, but I found the people I interacted with to generally be interested and smart.

Basically, the United flight holds short of runway 28 as he may need a little more time (this is the United flight CNN showed sitting there, probably).

The ATC controller knows something has happened because the first time we hear from 214 heavy, the controller tells the pilot emergency vehicles are on the way.

Then some captains on final announce they're going around and some ask for redirect (one clearly to San Jose). The controller then tells some flights on final to go around.

Finally he's directing rescue units to cross all runways where normally they'd hold at each runway to be directed.

Forgot one: "Go for profitability, make poor decisions, bounce along the bottom for awhile, and then liquidate."

The most likely path.

Those sentences do not say the same thing. Most worrying: "promoting" in the Google terms.

The UI for arrows was hard to figure out for a few minutes, but once I did I found it to be the right experience. Drag into space, you get an arrow to the same shape; drag to another shape, you get and arrow to that shape. That feels nice.

I appreciate the answers. Now I need to figure out a way to nudge the QA team toward learning to code.

On a recent Ruby Rogues podcast one of the guys mentions that if you want to see what software applications need to be build in an organization, see what people are doing with Excel.

"Excel is a coping method." - James Edward Gray II

This has definitely been the case in all the companies I have been at.

I'm a vim user. I'd use RM when pairing with someone not well versed in vim. Otherwise, I find it slow and difficult to work in.

They won't be able to exercise their vested options for several months (usually six, as I recall). And many won't have vested 100% yet. That keeps people around.

If you're so inclined, I'd also like to hear about the hot code reloading information you've found.

The top is "expertise" and the bottom is "how often I use it". Not clear, for sure.

There's a bad link in the article. The link to "Vim My new IDE" should be:

http://justinlilly.com/vim/my_new_ide.html

Congratulations for getting this out in front of people. Good luck. I'll be checking it out.

Isn't percentage more interesting that raw amount? It would be to me anyway.