Repairing Apple’s older laptops is notoriously difficult. They are not easy to work on. They are not designed to be: they are designed to be compact, durable, and look nice. Even apparently simple tasks can require removing dozens of tiny screws and disengaging delicate plastic tabs. Just before I went to college, I replaced a PowerBook G3 Lombard’s infamous right hinge; that was a fun two hours. Optical drives can’t be done in less than half an hour. Hard drives are sometimes a bit easier, sometimes not.

But a MacBook’s display is a special kind of difficult to remove. My father, who does Mac tech support and repairs for a living now, wouldn’t attempt the screen swap—it takes so long, that at the going labor rate, it’s prohibitively expensive. But “fools rush in”, so I volunteered for the suicide mission.

So I spent a day performing 61 “Very Difficult” steps forward then backward. It took five hours.

It seemed like a good idea to make a timelapse video of the process.

There’s also a 40MB higher-quality version, at a slower pace, so you can see what’s really happening instead of a crazy blur.

I used printed instructions from the magnificent iFixit.com. A few times, I had to look at the higher-resolution color pictures on my computer to see exactly which screw I was supposed to remove; the orange, red, and yellow diagrams don’t translate well from screen to greyscale laser printer.

As I removed screws and small parts, I taped them to the paper right next to the instruction, arranged in the same left-to-right order as their points of installation. The tape kept all the parts where they were supposed to be, and none got lost; I never confused similar-but-not-identical screws; I had parts exactly when I needed to reinstall them; and I moved completed pages aside, along with all their screws and parts. This tape trick came to me in a flash of insight while driving around town. I know I’m not the first person to come up with this, but I thought it was pretty clever, if I do say so myself ;)

I hit two snags in the repair process. First, after I swapped panels and reassembled the machine, the backlight didn’t work. You can’t quite see it in the video, but when I powered the machine up, the grey screen with Apple logo appeared like normal, but very very dimly. The LCD worked but it was almost impossible to see anything without the backlight. At first I panicked: did I break it? Did I fry something with static electricity? The inverter board that powers the backlight: is it more delicate than it seemed? As I reviewed the iFixit instructions to be sure I’d done everything right, I noticed a comment that explained what I did wrong. I took everything apart again, opened up the top half, and checked that inverter connector. Sure enough, it hadn’t “snapped”. I reconnected the essential cables and tested again, and the screen fired right up. Perfect. Whew.

The second snag was reassembling the front display bezel. It’s hard to see from the iFixit pictures, but between the white or black bezel and the metal frame there are twelve small grey plastic pieces. These grey bits are supposed to pop into the metal frame and stay there permanently. The protrusions on the back of the bezel slide into slots in the grey bits, holding on the bezel by friction. When I slid a credit card under the bezel, the bezel was supposed to detach from the grey bits. Unfortunately, what really happened is that the grey bits stayed tenaciously attached to the bezel, and I pulled up bezel and bits from the frame. I don’t know if this was because of aging materials, manufacturing variation, or (most likely) my sloppy credit card technique. The grey pieces wouldn’t snap back into the frame—they just bent. So I had to carefully pull all twelve off the bezel, bend their tabs back into shape, and pop them back into the frame. Finally I put the bezel back on. The iSight lens really didn’t want to stay in the bezel, so I had to flip the whole thing upside down to let gravity keep it in place. That was a small pain.

The hardest part was slowing down, taking my time, and working carefully and methodically. I’m a naturally impatient person. I hate wasting time, or spending more than is needed. And yet every time I tried to rush something (taking out a screw) or let my attention drift (looking at the various chips on the logic board, instead of the screwhead), I made a mistake (screw fell into the deep recesses of the case and had to be retrieved). I constantly had to make myself focus, slow down, and be patient. These are not things I usually do. The real challenge of this repair wasn’t the dexterity of my fingers, the keenness of my eyes, or finding a way forward when reality didn’t match the instructions. The real challenge was to myself: to sit quietly and do one thing at a time, carefully and attentively.

All man’s miseries derive from a single cause: the inability to sit in a quiet room alone.

—Blaise Pascal (unsourced)

Furthermore, x86 represents a worst case in the areas where it differs significantly from RISC-style processors…

Paul Barham, et al., Xen and the art of virtualization, SOSP 2003. Emphasis original, deliberately taken out of context.

If the Internet has taught us anything, it is that you can always get people to do what they already want to do.

Lawrence Lessig, NYTimes

The timing is very critical and synchronization problems happen a lot. There’s lots of hand-alternation; sometimes one hand is a decisecond early or late and I type a letter out of order. Sometimes I hit J instead of H because the “down” muscles are faster than the “left” muscles.

All these errors are compounded because I don’t actually know my password consciously. I’m not typing a word, I’m just activating a motor program. I don’t think “H”, I just put my finger “where it’s supposed to go next”. So all the error-correction in the cerebellum and motor cortex that I’ve built up from a decade of typing never has a chance to help.

Amusingly, I can type my ordinary and root passwords just fine under the influence of alcohol. So a complex password isn’t an IID for a computer.

On a darkly humorous note, many years from now, this may be an excellent stroke diagnostic. If I can’t type my password without concentrating, it’s time to call the paramedics.

“Joe, do you have a physical copy of this?”

I glance at the page of text on the screen, reach over to the heap of junk piled on top of the coffee table, carefully rummage around for a moment, and pull out the book in question. He doesn’t need to tell me what book he’s reading: it haunts my dreams still

Of course, last quarter when I was in the undergrad algorithms course, I borrowed his copy of the Kleinberg, Tardos book

(BSG is sweet)

This is impressive.

She majored in theoretical math, brain & cognitive sciences, and computer science. Yes, that’s three degrees.

This is dumbfounding.

She did it in four years.

This can’t be possible.

Bottom line for security & web developers: It’s Google’s database, they’ve been doing this for 3 years, only hashes go over the network, locally cached. It’s good stuff.

Bottom line for privacy-interested people: If you hit a suspicious hash prefix, you ask Google’s servers for the full hash. In theory this is enough for Google to do some analytics. Certainly it doesn’t directly reveal what URLs you are really visiting. Apple’s privacy policy does not discuss any sending of data to anyone but the site you visit (i.e. it is mute on this sort of feature). It further does not bind Google from misuse of anything they could collect. Mozilla’s privacy policy covers these bases.

Bottom line for anyone who has better things to worry about: It’s fine, leave the checkbox on, and if it ever warns you that you may be visiting a malicious website, stop and listen to it. You are probably not where you intend to be. Scott can explain.

I’m trying to use Mark Kenny’s Extended Comment Options plugin to automatically close comments on old posts. I used this plugin a long time ago, and it was great. But now, in WP 2.6, it seems to do exactly the inverse of what it says on the box: it closes my most recent posts and opens the oldest ones.

I don’t understand. Isn’t this just
UPDATE `wp_posts` SET `comment_status` = 'closed' WHERE `ID` IN (SELECT `ID` FROM `wp_posts` WHERE `post_status` = 'publish' AND `post_type` = 'post' ORDER BY `post_date_gmt` DESC) LIMIT 0,10

(Okay, it’s not quite that simple, because MySQL doesn’t do ORDER BY or LIMIT in subqueries… But it’s close! Temporary table?)

Has anybody got a good solution to this, better than a cron job to run that query?

Meanwhile, apologies to everyone who wanted to comment but couldn’t.