Skip to main content

(Insert Your Encryption Key Here)

I'm not going to post The Number, but I'm going to talk about it.

What another big shouting match the interwebs have found themselves in. Is it wrong to post The Number on public sites? I don't think so. Anyone who can use it already has to write software that the regular Joe will grab. The Number is just a political/social status symbol now. Publishing is the The Number is the anti-crypto1 parallel to the eye-liner high schooler shopping at Hot Topic. The point is making the point, more than what point exactly is being made.

So did the lawyers overreact? Of course they did, and consulting their clients before making moves on their behalf might be a decent idea. Maybe someone at the companies would actually realize the PR mess they might be stepping into. Maybe someone would say "Is the new technology stable enough to shake up our customers, yet?" Blu-Ray and HD-DVD are a techy's toy at this point, alongside wealthy status symbol usage. So, the large portion of the consumers who even use the technology are precisely those who know of and care about this story. When your ratio of Geek to Joe is that high on the Geek side, you need to act a little differently. Joe didn't even notice.

We sure noticed. Some of us noticed too much. I wish Joe noticed more.

Does anyone else mentally picture the AACSLA as Gollum and the The Number has their precious?

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad. Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems. There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day. The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad. You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You u