Deep sea divers don't get crushed like a grape.

The surface pressure on Venus is about 900 atmospheres. Divers would have to be at the bottom of the Mariana Trench (about 6.8 miles) to experience the same pressure which is far below what a diver can dive without a protective submersible. So, yes, they would get crushed like a grape.

Totally the thing of science fiction though. Even if you eclipsed the whole planet, it would take ages for it to cool off.

You'd also have to get rid of all the excess atmosphere somehow so a human on the surface wouldn't be crushed like a grape.

Speaking of cruft, ever see this?

That's a big fuck you to their customers.

If you're using a service for free, chances are you're not the customer.

That's a pretty myopic statement. It's not like gay people, when denied the right to marry, suddenly turn straight, marry people of the opposite sex, and have kids thus contributing to population growth; or when they do marry produce fewer kids than they otherwise would have. No, gay people will be with members of the same sex whom they love regardless of whether they're married or not. Marriage only confers legal rights (taxation, survivor benefits, military benefits, etc.) and has nothing to do with children.

Incidentally, some gay couples do choose to be biological parents. Marriage, sexual orientation, and having children are three distinct things that really don't have much to do with each other.

I've been using bazaar and it's everything subversion is, but better. It's had true renames since I've been using it and it really knows how to merge branches properly (which were the big big problems I've had with subversion).

... state frankly you are not answering any questions until you have counsel.

And even then don't answer any questions directly if you can manage it. Always communicate answers to any questions only to your lawyer who will relay your answers to the police.

Get every carrier to whitelist IMEIs rather than blacklist.

Why can't they just blacklist the phone's IMEI?

It should never happen in the first place. The specification should be crystal clear. Any ambiguities would have been worked out at the outset where I confirm that he really wants X.

... but it also sounds kinda lonely.

If you feel that way, then maybe software development isn't for you. I don't see it much differently that writing a book (in terms of the actual working environment). Presumably book authors do it because they love to write. The fact that it's a solitary job is irrelevant. I write code because I love to write code. I don't need my work environment to be a place for friends to socialize.

[H]ow does he do his job when you don't wish to attend the very short and brief meetings he's set up to find out how you're doing?

If he needs to know that, it means he doesn't trust me. If, however, he does trust me, he assigns a block of work X to be done by date Y and he can then essentially completely forget about me knowing I'll have it done by Y.

But normally you actually take some time to explain the problem and tell him when you'll pick it up or need it back by. You don't just leave him guessing.

Well, of course.... just like when the project is laid out at its inception. But, once laid out, there don't need to be daily meetings about it any more than I have to call my mechanic every hour. I think you're missing my point.

Because it's good to know how well the project is progressing? It's good to know if you're on target? It's good if something happens to someone or multiple people that you all know what has and hasn't been done and is left to do?

That's the project manager's job. I shouldn't have to care if he's doing his job. It's a matter of trust and competence.

If I have a good auto-mechanic that I trust, I know I can drop off my car, he'll diagnose and repair the problem, do good quality work, and not rip me off. That enables me to have the peace-of-mind to not have to care about his work or how he gets it done.

I should have that same level of trust in everybody I work with so I don't have to care. I think part of the problem here is that the phrase "I don't care" is seen negatively in common use. I don't mean it that way. If I don't care about your work, it's because I know you'll do a good job (just like with my auto-mechanic). That frees my time up to work on what I need to work on.

If I have to care about your work, it implies I need to baby-sit you because I don't trust your quality of work or that you'll get it done on time.

[Good developers] are able to leverage the power of a good team to boost their own performance and their coworkers to new heights they couldn't achieve on their own.

You make it sound like a team is some kind of social program (no developer left behind). It's not. A team is a part of a company whose goal is to make money -- with any luck, enough of it to retire early.

Until your code runs into a conflict with someone else's code because of a lack of communication.

That should have been worked out during the design phase.