The signs of the apocalypse have been around for thousands of years. What makes these signs any more relevant than the other signs?

Chances are, you don't know anything about databases. JetProfiler will show you the crappy queries you're using in an easy-to-understand way so you can fix your stuff and make everything faster.

AFAIK, no such tool exists for Postgresql.

As a bonus you don't have to deal with the annoying psql/pgsql crap, which for some reason drives me bonkers. I mean come on, make it psql or pgsql, not both. WTF?

Austin, as usual, is full of shit.

Clinton said she never sent classified emails from her server. However, she never said that she didn't receive classified emails on her server. As anyone in the government industry knows, when you get classified emails on an unclass system you have to "sterilize" your servers.

Did she do that? Probably not.

I guess that's why she was such a crappy SecState - everyone's intelligence services were reading her emails.

One funny thing about the Obama White House is that past Republican behavior has become the new bar by which Democrats are judged - even by Democrats.

"But - but - Dick Cheney did the same thing!"

Democrats have already lost.

#3 -> you have to know it's coming and be able aim/fire at it. How fast can you identify, track, and shoot down something when you don't know what you're looking for and where it's coming from? Plus they'll probably come at night, when it's hard to see.

#4 -> See above.

Maybe they could shift everything 100 feet to the left in case of emergency. Would that work? It probably wouldn't be reliable - it depends on how the drone is using GPS.

There are two ways they could do this, as far as I can tell:

1. disrupt the onboard electronics to kill the power
2. spoof GPS so the thing goes somewhere totally different

You could do #1 as well by having nets spring up/out - basically have a physical barrier. The question is how would you deploy anything fast enough to catch an incoming drone? Even an energy weapon needs time to find, track, and fire.

#2 is easier, because most drones today use GPS. Just have the white house have a GPS signal that overloads anything the drone has. In fact, they could fuzz DC out of GPS, which would be the safest option.

#2 will cause drones to use an inertial system, which would then be hit with #1.

Really, they need a perimeter of cameras to track any fast moving objects from 1 mile out right down to the white house. That would probably give them enough time to figure out the vectors so they could actually do #1.

Geez, who knew that writing 'NSA' to 0xdeadbeef over and over would give you kernel access? Those NSA guys really broke into everything.

The SPOD is from NeXTSTep. I remember seeing it often when using the old magnesium cube.

Another Democrat blaming bush for Democratic shortcomings!

God damn, grow some adult pants and take responsibility for your decisions.

"If it ever becomes the default on consumer phones, for liability reasons or for whatever, the first thing people will learn is how to disable it so they can save battery power."

You mean consumer phones like the iPhone?

I work in an office where you can work at home. It's much, much better to work in the office. There's a lot of cross-talk, which makes our product(s) better.

That said, WFH is good when you need to get stuff done that's task-specific.

As a blanket policy WFH can work, but if everyone works from home then you have strong online collaboration tools. For a place the size of Yahoo WFH across the board is a "I don't feel like working" policy.

Yahoo was stagnating for years, so it's unclear what these people who were WFH were actually doing. If they were kicking out killer shit than the policy would be justifiable - but they weren't.

Actually, I've done all that. It's really not that hard to estimate, unless you don't pay attention to how long it takes to do stuff. It's not like you're trying to figure out how to fuse atoms, and have to build the manhattan project from scratch.

Writing something new is more difficult, but when you break it down into chunks it becomes easier. You do have to have a good understanding of how you work.

Just like anything, it takes practice. If you have enough people estimating you can bayes the answers, sort of.

Part of being a software professional is understanding how long it takes for you to do things

If you don't know how, go read a book. It's not hard. The money that's used to pay you depends on your estimate being somewhat correct.

Imagine how upset you would be if you asked for your paycheck, and payroll said "we're not sure when we're going to pay you, but it should be sometime soon."