No comment:

"We wanted to do something that would market augmented reality in a way that's... meaningful. We were like, wouldn't it be awesome if you could look up her skirt, or take off her clothes?"

(via BBG)

Stop, you’re killing me.

Titled "Koisuru Hello Kitty," the play is described as a "school love comedy" that deals with romance and friendship. The main character is a Hello Kitty doll that turns into a human...

I think Girls’ Generation could sell anything.

Emacs 23 natively uses Unicode. This means I can run it in a Terminal window, like God intended, and still have full Japanese support. Previous versions did funky Shift-JIS conversions that made its behavior… “eccentric” on a Mac, especially with cut-and-paste.

Now all I have to do is strip out all of the cruft from the elisp directory, and I’ll have the perfect text editor. Actually, it’ll be easier to delete everything and just add back the non-cruft as needed. There’s not much that I don’t consider cruft, so it will be pretty darn small.

[side note: a release comment says something to the effect that the internal encoding is a superset of Unicode with four times the space, which would make it a 34-bit system. WTF? Update: ah, I see; UTF-32 has a lot of empty space, with only a bit over 20 bits allocated in the Unicode standard. UTF-8 was also designed with considerable headroom, which is no surprise, given that it was invented during dinner by Ken Thompson.]

I am quite certain that 15 of the 28 people who show up in a Facebook search for Ooma employees are not, and never have been, associated with the company in any way. Which leads to the question, “why?”. We’re not that cool.

You are not of Latin heritage, and neither is the song Cosmos. Not attempting to mimic Momoe was a good choice, at least, since she’s a bit out of your league, and you did deliver the best vocal performance on the album.

Keep an eye on Linlin, though; with better material and some practice, Junior Panda could eat you.

Korea is kicking your ass.

more...

I don’t want a database guru. I want a database ogre, who lives in a dank, dark cave lined with the bones of developers who think they can write their own queries and release them to Production.

During my latest round of load-testing, I discovered that one particular client-driven query degrades rather seriously under load. As in, fifteen minutes to use a unique device ID to look up the matching unique customer ID and a single string related to RMA status. Part of the problem was that the dev was looking in the wrong place, but the main problem was that he didn’t understand the data, so the query was written in a way guaranteed to maximize search time. (rant about poor schema design saved for another day…)

I am a SQL caveman. My formal training in database technology began and ended with a single COBOL class in the mid-Eighties. I rewrote the query and dropped the time to 0.062 seconds under the same heavy load.

Four orders of magnitude? Time to feed another dev to the ogre!

(and, yes, the checkin comment attached to this query begins “optimized the sql query for …”. The sad thing is that, relatively speaking, this is a true statement; his previous code was worse)