evilbit

Conversely, the fact that you don't have a LinkedIn account is a red flag to many employers potentially looking to hire you.

Look on the bright side: she was wrong on tips: they're calculated on net price and need not include the tax. If you're tipping based on total (incl. tax), you're tipping few % more than you intended to.

Not sure what you mean. Visual debugger (with breakpoints and all) in FireBug is almost on par with IDEs.

Liberation/spreading democracy :)

You are, of course, correct, but I am yet to come across a single production system that uses singleton in that manner that isn't driven by Spring or some other IoC container.

Fact of the matter is: canonical implementation of singleton is with getInstance(), so when people rail against Singleton, the getInstance() implementation is implied.

No.

It sucks. It blindly groups messages by subject, regardless of whether they're actually related, e.g. for me it grouped all empty subject messages from a span of 6+ years that I've had this Gmail account (I never delete email).

If Ruby on Rails causes nothing but headaches for those who insist on silly frilly things like data integrity, I will theorize that perhaps the problem lies with RoR, not foreign keys.

You probably don't actually need a database at all , given that the integrity of data stored is not paramount. You don't get any points for "We have this data. We have no way of assuring it's correct or is what we want it to be - but we have it!"

On the other hand, given that most start-ups don't bother with things like a business plan (at least one which doesn't end with "Step 3. ????? Step 4. Get bought by Google"), perhaps it's only appropriate that such start-ups do away with other fundamentals of reality, such as data integrity.

i, too, am a very happy long time (13+ years) vi/vim user. if you haven't ever used a powerful keyboard-only text editor such as vim or emacs, you simply have no idea what you've been missing.

quit being a curmudgeon. this is one happy human sharing something they love with others. if you don't want any of it, just keep moving. your negativity does not advance the human condition.

pair programming went out of fashion for the same reason foosball tables in the office did: it was a dumb idea somebody concocted in the haze of the dotcom boom. reality eventually reasserted itself, we grew up, and learned to work like professionals.

if the only way to keep your developers busy and not goofing off is to have someone looking over their shoulder, then you, my misguided friend, fail as a leader.