Casttoo

A picture is worth 1,000 words. Save your breath and explanations by showing the world what's going on under that cast. Had a really bad break that you want to show off? Send us the digital file of your x-ray, and we'll send you back your break in print, ready to be applied directly to your cast.

Rap Lyric Generator

The lyrics presented in Figure 5 revolve around the theme of receiving oral sex, alcohol, and going to the club. Thus, words like "club" and "bust" have relatively high TFICF scores (TFICF=1.83e-4 and TFICF=1.67e-4) than other non-related words (TFICF=4.24e-7). The lyrics presented in Figure 6 also generally revolve around the themes of sex and partying.

Chef at Chelsea restaurant offers customers a taste of cheese made from his wife's breast milk

Chef Daniel Angerer is letting diners at Klee Brasserie munch on cheese made from his wife's breast milk.

"It tastes like cow's-milk cheese, kind of sweet," he told The Post.

Breast milk doesn't curdle well due to its low protein content, so a little moo juice has to be added to round out the texture, Angerer said.

After blogging about his efforts with the human cheese, customers started demanding a sample, he said. "The phone was ringing off the hook," the chef said. "So I prepared a little canape of breast-milk cheese with figs and Hungarian pepper."

Since the restaurant began offering customers a taste, Mason has been inundated with creepy queries, she said.

"Some people who clearly have issues have e-mailed me saying, 'I wasn't breast-fed as a child, so can I taste your breast milk?'", she said.

Mason politely declines the offer. "I'm not here to walk people through their psychological problems," she said.

Crime Over Spilt Milk

After Toni Tramel, 31, was arrested last Thursday for public intoxication, [...] Tramel "took off her bra, grabbed her breast and squirted breast milk, hitting me in the face and neck region," reported Brown. Tramel attempted a second lactation assault, "but was unsuccessful," added Brown. [...] As for Brown, a jail press release noted that the officer was successfully able to "clean the bio-hazard off her."

Scott and Scurvy

I had been taught in school that scurvy had been conquered in 1747, when the Scottish physician James Lind proved in one of the first controlled medical experiments that citrus fruits were an effective cure for the disease. From that point on, we were told, the Royal Navy had required a daily dose of lime juice to be mixed in with sailors' grog, and scurvy ceased to be a problem on long ocean voyages.

But here was a Royal Navy surgeon in 1911 apparently ignorant of what caused the disease, or how to cure it. Somehow a highly-trained group of scientists at the start of the 20th century knew less about scurvy than the average sea captain in Napoleonic times. Scott left a base abundantly stocked with fresh meat, fruits, apples, and lime juice, and headed out on the ice for five months with no protection against scurvy, all the while confident he was not at risk. What happened? [...]

In the second half of the nineteenth century, the cure for scurvy was lost. The story of how this happened is a striking demonstration of the problem of induction, and how progress in one field of study can lead to unintended steps backward in another.

An unfortunate series of accidents conspired with advances in technology to discredit the cure for scurvy. What had been a simple dietary deficiency became a subtle and unpredictable disease that could strike without warning. Over the course of fifty years, scurvy would return to torment not just Polar explorers, but thousands of infants born into wealthy European and American homes. And it would only be through blind luck that the actual cause of scurvy would be rediscovered, and vitamin C finally isolated, in 1932.

Last night, a bike locked to the same parking meter as mine had its seat stolen, in a graphical demonstration of the principle that you don't have to run faster than the bear, you just have to run faster than your friend.

• 20:34 @jennamarino I did hit an hour long mechanical failure in NYC, but I blame that damned city and not the train. #

Dear Lazyweb,

How do I extract my iPhone SMS logs as plain text, or XML, or anything else greppable/archivable on my desktop computer?

• 15:23 On a train to Philly! I don't want to be a railway superstar like @matthewjweaver, but it's pleasant enough so far. #fb #

Version Control Systems (git, svn, perforce, source safe, cvs, darcs, etc) are software packages that checkpoint your source code (or other documents and files) while you're working. They let you restore older versions, retrieve groupings of files, etc. Generally they have a 'diff' mechanism, so that rather than saving the entire file each time a change is recorded, it instead saves only the little portions that have changed.

All VC systems have one aspect to them that I personally find to be annoying. All of them require you, as the developer, to actively check in your code. Personally, I see this as a major flaw.

A VC system should be transparent. It should be checkpointing your code while you're working. All of these autocheckpoints should be considered to be "experimental" or even "broken". They are not there as release-candidate code, but rather "i'm still working on it" code. Perhaps these are even a private branch or fork, to be merged back in when the developer actively marks the code for others to use.

You can use backup systems like "Time Machine" for example, but they're detached from the concept of it being your source code, and generally are pretty hevayweight.

Here's one way I think this could work, using existing technologies:

1. A distributed source control system like GIT for example, would probably be best for this. All of the auto-checkins happen to the local repository. This can also be accomplished with a non-distributed VCS like subversion by branching the code.
2. A small number of scripts wrap the VCS/VCS Manager:
   1. Auto-checkin - run every N minutes (5-10?) - does a checkin to the local repository, marked with the current date/time as experimental/broken
   2. Active Mark - run by the developer to mark a specific milestone - optionally joins the code back into the main branch, or pushes it to the central repository
   3. Retrieve - gets an old version of the source at a certain time/date/mark

So the concept is that you start the auto-checkin thing, when you start your development session, and stop it when you're done. During that time, it will automatically check in your code, so at no point are you unable to step back in time. Screw up your code bad? it's just a step away from retrieval. Want to restart from yesterday? it's just a step away. But the important thing, and this is key, is that at no point along the way was it necessary for you do to actively checkpoint your code.

We have computers to help us. Why not let them help us with this aspect of development to?

The more I think about this, the more I think I need to implement it. It shouldn't be too difficult to implement with either Subversion or GIT at its core.

Mood - optimistic
Music - Easy Star All-Stars - "Dub Side Of The Moon"

• 08:54 Please don't be ignorant about #healthcare reform! Educate yourself on with some facts: bit.ly/coLiDt #hcr #fb #in #