Tim Chase posted an interesting list of potential interview questions to comp.lang.python:

While I haven’t interviewed precisely for Python, I’ve been on the other (interviewing) end and can offer a few of the sorts of things I ask. I don’t expect perfect answers to all of them, but they show me a range of what the interviewee knows.

They are grouped by difficulty (basic, broader, advanced, etc.) and seem to be pretty reasonable. Worth taking a look if you want to assess where you fall in the spectrum of Python coders.

Quoth David Pogue:

But I’ve got a lot of questions, too—a lot of them that I don’t have answers for. In fact, I’ve been keeping a little list.

Some of them are answerless because nobody knows the answer. Some may have answers, but only industry insiders know what they are. And still others are answerless because they’re incendiary hot-button issues, and there’s no consensus.

I thought: What better way to find the answers than to lay out my list for the reading public?

Check out Pogue’s Imponderables. It’s an interesting list.

Christian Flickinger talks about setting your Facebook status via the API:

Welll, it appears that one month after Facebook asked me, and others, to remove my little cURL ‘hack’ for updating your Facebook Status, Facebook has finally implemented a users.setStatus() method in their API.

Interesting.

Quoth Mark Pilgrim:

I have nothing to say about the iPhone that hasn’t been said already. Apple made it very clear what they were offering: a carrier-locked, closed-development mobile computing device where every aspect of the user experience would be controlled by Apple. I’m told it can also make phone calls. If that’s what you want, then buy it. If not, then don’t.

Read the whole thing.

I stopped by…

…the Fifth Avenue Apple Store.