bravesirrobin

I have to admit that I'm impressed at how well the system they build compensated for the mechanical failure. It looks like they have some good people building things.

One aspect that's worth consideration is the private/corporate aspects of spaceflight. When there were failures in Apollo and the shuttle, the public had a right to know everything that happened since we'd paid for everything. SpaceX has been super cool about disclosure here, but how long can we count on that? At some point, there's too much money at stake for them to maintain full transparency.

I just love this bullet point: * Maxwell Technologies Specified, Controlled, Tested and Guaranteed

So, I suppose if you experience a nuclear detonation and the chip doesn't go off, you get your money back?!

This is the best advice of all that I've read in this thread. I wanted to add that strategically, you definitely want to have that job in hand before you quit.

Firstly, if you're interviewing at other places when you already have a job, they are usually willing to skip references and hire you based on tech knowledge and interviews alone. Grabbing tech talent these days is really tough, and most recruiters know they have to be discreet with people transitioning from a current job.

Secondly, the job you're at is likely to give you a crappy reference after you give notice. You want to be well on your way to making that next employer your next reference as soon as possible. The alternative, i.e. being unemployed with them as your most recent references, makes you harder to hire.

Dr. Egon Spengler: There's something very important I forgot to tell you.

Dr. Peter Venkman: What?

Dr. Egon Spengler: Don't cross the streams.

Dr. Peter Venkman: Why?

Dr. Egon Spengler: It would be bad.

Dr. Peter Venkman: I'm fuzzy on the whole good/bad thing. What do you mean, "bad"?

Dr. Egon Spengler: Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light.

Dr Ray Stantz: Total protonic reversal.

Dr. Peter Venkman: Right. That's bad. Okay. All right. Important safety tip. Thanks, Egon.

Nice, but I'm not sure this resume would get him an interview at Google today.

One thing that CSS does especially badly that tables do well is correlated sizing. It's easy with tables to make all the elements in a layout row all have the same height. Doing the same in CSS is possible but requires so many hacks that the net result makes you feel dirty.

I've watched this war for years now, and just wish both sides would give some ground. As long as you do your layout with the fewest amount of tables needed (trending toward zero), the you shouldn't need to guilt yourself out about it.