jones_supa writes: TempleOS has become somewhat of a legend in the operating system community. Its sole author, Terry A. Davis, is a special kind of person, who has a tendency to appear in various places with a burst of strange comments. Nevertheless, he has spent the past 12 years creating a new operating system from scratch, and has shipped a functional product. An article takes a constructive technical look at the internals of TempleOS: installation, shell, file explorer, hypertext system, custom HolyC programming language, and interaction with hardware. The OS ships with a suite of several tools and demos as well. To see the sheer amount of content that's been written here over the years, to see such effort expended on a labor of love, is wonderfully heart-warming. In many ways TempleOS seems similar to systems such as the Xerox Alto, Oberon, and Plan 9; an all-inclusive system that blurs the lines between programs and documents.

Bennett Haselton writes: I would be in favor of a regulation requiring cell phone stores to have replacement phones on hand, for any phone model covered by a customer's insurance policy. Then customers who have insurance protection on their phones could get the damaged phones replaced instantly, and the replacement phones that are normally mailed out by overnight mail to customers under their protection plan, could instead be mailed to the stores to replace the one they just gave out to the customer. Read on for the rest of Bennett's thoughts

We've talked in the past about what kind of questions should be asked of potential developer hires, and how being honest in exit interviews probably isn't worth the potential damage to your career. We're also familiar with the tricky questions some interviewers like to throw at people to test their thinking skills, and the questionable merits of gauging somebody's skillset through a pointlessly obtuse math problem. But there are also shady employers who conduct interviews to try to mine your knowledge and experience to find free solutions to their current problems. An actual job may or may not be on the table, but if they can get what they need from you before hiring, then at the very least your bargaining position will have gotten worse. Have you dealt with situations like this in the past? Since you can't know for sure the interviewer's intentions, it's tough to provide an answer demonstrating your abilities without solving their problem. "Before asking about the fixes they’ve tried, start by acknowledging the depth of the problem and find out whether the manager has the resources to solve it. Then, just like a consultant, use their answers to highlight your experience and explain the approach you’d take." You could also try explaining how you've solved similar problems, which won't necessarily help them, but will demonstrate your value. Of course, one of the biggest challenges is determining when somebody is getting a little too specific with their interview questions. What red flags should people keep an eye out for?

Not even the tranquility of FarmVille can save you from the long arm of debt collectors. Melanie Beacham says that a collector from MarkOne Financial contacted her relatives about her past due car note via Facebook. She is filing suit alleging that the company is harassing her family. Tampa based consumer attorney Billy Howard of Morgan & Morgan says, "Now Facebook does a debt collectors work for them. Now it's not only family members, it's all of your associates. It's a very powerful tool for debt collectors to use."

mytrip writes "A Polish priest has installed an electronic reader in his church for schoolchildren to leave their fingerprints in order to monitor their attendance at mass. The pupils in the southern town of Gryfow Slaski told the daily they liked the idea and also the priest, Grzegorz Sowa, who invented it. 'This is comfortable. We don't have to stand in a line to get the priest's signature (confirming our presence at the mass) in our confirmation notebooks,' said one pupil, who gave her name as Karolina."

Adam Dunkels writes "Inspired by the Twitter-sized program that crashes Mac OS X, I just wrote a really, really rudimentary IP stack called twIP, small enough to fit in a Twitter tweet. Although twIP is very far away from a real IP stack, it can do the first task of any IP stack: respond to pings. The entire source code can be found in this 128-character-long tweet. For those who are interested in low-level network programming, a code walkthrough with instructions on how to run the code under FreeBSD is available here. The FAQ: Q: why? A: for fun."