I just received this email. Details have been redacted to anonymize it. Rant follows.

From: [CUSTOMER NAME REDACTED]

Matt,

Sorry for bothering you, but I found your CV online and saw that you used to be the Lead Developer for [PRODUCT NAME REDACTED] a few years back. My wife owns a small [BUSINESS TYPE REDACTED] in [LOCATION REDACTED] and we recently migrated to [PRODUCT NAME REDACTED], which was a fluid easy process, no doubt due to some of your work — thank you for that!

One question I’ve had since moving over though is regarding their scheduling and if there’s any way to make it play with google cal or ical — I’ve asked [PRODUCT NAME REDACTED] and the techs there and it seems to be a pretty straight forward “no”… but knowing the internets and that “anything is possible” more or less, I gotta think that there must be a way to write some kind of script that could at least scrape the [REDACTED] calendar and at least provide a way just subscribe or “view” the schedule– I’m not even talking about two-way functionality… viewing would be a huge help for us and her colleagues. Moreover, my guess is that we aren’t the only ones who would love to have a way to check the schedule that wasn’t dependent on logging in to [PRODUCT NAME REDACTED], especially since they have yet to offer any mobile apps for smart phones, and that any script/app/plugin/program that’s created could even be shared with other [REDACTED].

Anyway… I won’t carry on as this is a straight cold call… but if you do have any advice and have a chance to respond, I would be most grateful!

Cheers!

[CUSTOMER NAME REDACTED]

This is jaw-droppingly awful. Let me count the ways:

1. This guy is asking me to think about a job and a piece of software that I stopped working on years ago. Since a programmer’s job is, in many ways, to think, he’s essentially asking me to work for free.
2. He is fishing for me to contradict what he has been told by the company I used to work for, which would be a totally unacceptable thing for a programmer to do even when still employed by said company.
3. Even if I was willing to think about a software project that I haven’t looked at in years and undercut my former employer by contradicting them, it’s likely that the project has changed since I left in ways I cannot even begin to imagine. So even if I did remember enough about the project to confidently answer his question, I would probably be totally wrong.
4. What would he do if I told him it would be totally easy to implement? Go back to my former employers and tell them that some random who used to work for them said that it would be easy? Is that going to make them change their mind about implementing this feature? No.
5. Anything is possible? On the internets?

This is the kind of obnoxious customer that small software companies just don’t need. End of rant.

As promised, here are the results of two totally unscientific surveys, one conducted at PyCon 2011 and the other over Twitter just a few days ago, about the behavior of else in Python loops. The results show that only 25% of respondents know what else in a Python loop actually does, and 55% think they know but are wrong.

Phobos Labs’ nine years of sleep inspired me to make this chart of the last eleven years of my email. Read more….

The Mathematician’s Dice are now for sale to the general public!

The Kickstarter project to get these dice to market was an amazing experience. I plan to write the whole thing up and post it here soon.

Here’s a little gist that I wrote to illustrate the difference between MongoDB‘s use of degrees vs. radians in its non-spherical and spherical geospatial queries:

I’ve already tweeted about this, but for all you Python programmers who have gotten indigestion from the complex process of installing virtualenv and virtualenvwrapper, check out brainsik’s virtualenv-burrito. It wraps up both tools and installs them for you in a single step, no thinking required.

A while ago I designed the Mathematician’s Dice (on Shapeways), dice with i, 0, 1, φ, e and π on them. Now I’ve launched a Kickstarter project to get a run mass produced! Check it out, and donate or pass it on to friends:

I am going traveling very soon, so things will get pretty quiet around here. My posts here are split up into three categories, and each has a separate feed:

• Essays (subscribe here), my longer, in-depth writings, usually about technical subjects.
• Travelog (subscribe here), which is where I have written about my travels. Although will be traveling soon, I’m not sure if I’ll continue to write travel log entries.
• Blurbs (subscribe here), mostly links to things I find interesting, with very short commentary. For the last few months I’ve been posting interesting links & short commentary via Twitter instead, so if you like my blurbs, or want to respond to anything on here, you could follow me on Twitter.

There’s of course also a master feed for all posts. You can follow my posts on Digg, or follow my account on the awesome soup.io, which aggregates this blog, and my twitter, t-shirts, 3-d printing, and various other online presences. (Update 2011 April 6: Digg has removed import by RSS)

Those who followed Is Git really better than X will enjoy this interesting article by Armin Ronacher on the finer distinctions between Git and Mercurial’s branching. (via brainsik)

The answers to Richard Thaler’s Edge 333 question are all worth reading, but Nicholas G. Carr’s thoughts about metaphors for the brain is especially good:

I think it’s particularly fascinating to look at how scientific beliefs about the functioning of the human brain have progressed through a long series of misconceptions.

Aristotle couldn’t believe that the brain, an inert grey mass, could have anything to do with thought; he assumed that the heart, hot and pulsing, must be the source of cognition, and that the brain’s function was simply to cool the blood.

Descartes assumed that the brain, with its aperture-like “cavities and pores,” was, along with the heart, part of an elaborate hydraulic system that controlled the flow of “animal spirits” through the “pipes” of the nerves. More recently, there was a longstanding belief that the cellular structure of the brain was essentially fixed by the time a person hit the age of 20 or so; we now know, through a few decades’ worth of neuroplasticity research, that even the adult brain is quite malleable, adapting continually to shifts in circumstances and behavior.

Even more recently there’s been a popular conception of the brain as a set of computing modules running, essentially, genetically determined software programs, an idea that is now also being chipped away by new research. Many of these misconceptions can be traced back to the metaphors human beings have used to understand themselves and the world (as Robert Martensen has described in his book The Brain Takes Shape).

Descartes’ mechanistic “clockwork” metaphor for explaining existence underpinned his hydraulic brain system and also influenced our more recent conception of the brain as a system of fixed and unchanging parts.

Contemporary models of the brain’s functioning draw on the popular metaphorical connection between the brain and the digital computer. My sense is that many scientific misconceptions have their roots in the dominant metaphors of the time. Metaphors are powerful explanatory tools, but they also tend to mislead by oversimplifying.

What other contemporary metaphors are misleading us about our world today?