I pick up every coin I find and put it in a large jar. Once it's full I take it to the bank and, though it really upsets the teller to have to deal with it, I end up netting around $300. Granted it takes a few years, but every little bit helps. :\

To quote Bob Fosse: I don't want people who want to dance; I want people who *need* to dance. That is what I look for during an interview, someone who clearly loves what they do and doesn't just sit around waiting for orders or just did whatever was told of them. I typically ask them about a project they were on, and if they get into the details, even if it's not exactly specific to programming but that they understand the "big picture", as well as their role in it, and look to see the eyes light up. It's especially Then I move on to the question that a lot of people don't expect, surprisingly, but is very telling: "What got you into programming?" Any flavor of "because it's really really cool" works; sadly a lot of responses are "it was either this or becoming a lawyer | dentist | whatever".

I have an ipass, and it's entirely hidden by the rear-view mirror; if there was in fact a camera, all it would capture is the back (front?) of the mirror. As I recall, the installation instructions specifically suggested that spot as being the most unobtrusive.

Just one small nitpick...sqlite is really meant as an embedded database into an application, it's not a full-fledged database like any of the others mentioned (it doesn't have networking, for example). I suppose you could be scaling up from an embedded sqlite db, but that suggests your application has gotten so big that an external database is necessary.

It's also one of the backing store options for Apple's Core Data framework.

I was working in World Trade Center #1, on the 95th floor, during the nor'easter of 1992, which if I recall was the remains of a hurricane. It was quite an intense experience; we had the space-saving "rolling file cabinets" that were rolling back and forth on their own, with one finally derailing and spilling files onto the floor (guess who had the job of cleaning it up). Bathroom stall doors were opening and closing by themselves, you could hear a definite creaking from inside the walls, and they were always shutting down the express elevator due to flex.

The thing that was really wild, though, and sadly not to be seen again, was looking out the window and being able to easily make out the other tower swaying as well. I had to keep telling myself "the buildings are designed for this...it's okay!" until it was time to go home.

Funny enough, I just set up an Ubuntu box and decided to grab JDK 7 without knowing that today would be the day it was "released". As such, I downloaded it directly from Oracle/Sun/Java/Whatever..

Note, I then installed Eclipse Indigo, which was having some problems with some of the plugins. I added the following line to the eclipse.ini file and the problems went away:

-Djava.util.Arrays.useLegacyMergeSort=true

Everything's working fine now.

Note: I have absolutely no position on this issue; I am not taking sides at all. My only question is how you can be certain that two programs are identical when you presumably don't necessarily know how each was compiled. Assuming all you have of rybka is a binary, but have the source to fruit, how could you be certain that you could get the code to compile in such a way as to produce identical assembly as disassembled rybka. Assuming a general standard IA32 machine, you still presumably have a lot of opportunities for variation in output from compiler to compiler, version to version, and even flags to flags.

I restate that I have no horse in this particular race; I've read of similar scenarios where a program was discovered to be a clone of another, and I've never understood how they can tell.

Considering it's IBM's 100th birthday, it should be pointed out that a lot of the concepts TFA talks about were being done by groups like SHARE long before Linus was even born.

I worked for a large organization in Chicago that had the "gold" IBM support contract back in the early 90s; they would show up at 2 am Sunday morning to replace a keyboard if necessary. Our main contact was a guy who had been with the company for 30+ years and he would mention some of the things he'd had to fix, in addition to the standard computer stuff: scales for weighing meat in the meat packing district and the thing that was most surprising: the clock on the Wrigley Building. Apparently IBM didn't actually out-and-out make the clock mechanism but had bought some company that had and they inherited the support contract. He mentioned having to get some gears specially made when it broke down.

The thing I thought was so ahead of its time was the wireless device he had that was essentially a large, two-line blackberry that he'd carry on his shoulder with a strap; it would beep and he'd flip the cover open, read the message, then type some sort of response. I remember he'd use it to order parts and within an hour(!) another guy would show up with them, a new ps/2 mouse, a monitor, or a reel-to-reel tape drive for the as/400. I was surprised IBM never thought to market that device; much like Apple is reluctant to talk about their ipod touch-based POS terminals, he wasn't too keen about showing it off or even talking about it.