Breaking news : junk food is junk!

Exactly. I've never understood why they had bonuses in the first place.

My job is to be a developer, and thus to produce good, maintainable, efficient code. If I fail at this, I'm fired. If I succeed, I just did my job, and thus get a salary for this.

The job of bankers is to produce money from money. It's just their job, and I'm pretty sure it doesn't need more intelligence than to produce great code. But if they fail at doing it, they just ask governments to help them, and still keep their salary. And if they succeed, they get huge bonuses.

Plain stupid.

10 k inches? meters? feet? yards?
k means kilo (1000). It's not a distance unit. I guess it's 10 km (1000 meters). Isn't it basic stuff that every nerd learns at school, at the age of 8 or 9 years?

Yeah, but, in other news:

Extra! Extra! Read all about it.
Pinball wizard in a miracle cure.
Extra! Extra! Read all about it.
Extra!

(The only song I know the lyrics by heart)

That's nothing : in an episode of NCIS, they have to crack a remote system (or prevent a cracker for cracking their own system, I don't remember), so they employ the usual technique : they type very fast on the keyboard.
But since they're really in a hurry, they enhance this well-known technique : Abby and Mc Gee both type, at the same time, very fast, on the same keyboard. Go beat that!

This would introduce a bug in your application, since Calendar.getInstance() always returns a new instance, containing the current time at the moment it is created. Storing it in a static variable and reusing it would return the same time forever.

Moreover, Calendar is not thread-safe and is mutable, so storing it in a shared static variable is a really bad idea.

I suffer from stammering, you insensitive clod!

Subversion calls this a feature branch. You branch the trunk, which stays open to the public. You make regular commits to the branch, and when the large refactoring is done in the branch, you reintegrate the branch into the trunk. The trunk remains stable during the whole process.
How is it different with a distributed system?

Huh. You might well be the one who doesn't understand what goes on behind the scenes. Just read the source code:

        public void ensureCapacity(int minCapacity) { // ...
                int newCapacity = (oldCapacity * 3)/2 + 1; // ...
        }

It thus allocates half the current size of the list each time the capacity is reached, and not just 6 slots.