The Whistler

January 30th, 2012

I have sensitive hearing - I can sleep in a room with the lights on without issue, but any regular source of noise and no luck. The same goes for concentrating in general.

So today I am working at home, troubleshooting a lab, when I hear a high-pitched whine. Seems to be very nearby. And of course, once I hear it, I cannot stop hearing it - so I have to seek it out and put a stop to it.

I'm surrounded by at least three working computers, but upon aural inspection none of them seems to be the source of the whine. The ventilation system? No. I walk in and out of the room and around within and the whine is loudest at my desk.

Cell phone? No. iPod? No. What the heck...?

It's my Diet Pepsi. I had screwed the cap back on firmly enough to prevent spillage, but apparently not firmly enough to create an air-tight seal, and it's carbonated enough to force out a thin, reedy whine.

Which I dispose of with another firm twist. And back to work.

Flying in a B-17: Part 1

May 13th, 2011

B-17G

Last weekend, my plan was to finish building the chicken coop. I got up earlyish on Saturday to borrow my father-in-law's van to pick up a sheet of roofing material. He came with me to look for fencing material.

Supplies purchased, we went to my house and worked on moving the roofless coop from where I was building it, near the garage, to the spot my wife selected, out in the back yard. We were just starting move it when I heard the rumble of big radial engines coming closer. DC-3? There are a couple of those in the area. But this was louder, something with more than two engines. Which doesn't leave many options, and all of them are enough to make me drop a chicken coop on my foot (nearly) to get a look. We have trees in and around our yard, so you have to be quick to see something flying overhead. And coming out past the palm trees was a big, silver B-17, flying straight over the yard and towards the northwest. I explained what it was to my father-in-law, and I that I had read a small notice in the local paper about a B-17 at Hayward. And that you could take a flight in one, but for a big chunk of cash. I was just hoping to drag the family out to take a tour of the old girl.

Anyway, we had a chicken coop to move. Then it was time to take the girls to gymnastics and get on with the day. My mother-in-law wanted to take the girls shopping, and when she picked up the girls she handed my wife an envelope "of some paperwork for Neal." Which turned out to be a small stack of large bills and a note to enjoy the flight. I stared at it, not understanding. My wife, possessed of far more sense than me, realized what it meant, while I was still trying to figure out where the guy wanted me to travel to, and for what possible reason. After she patiently explained it to me, I think I stared and babbled for a few minutes. Then we rushed home and I made some phone calls. Wait; I think we stopped for paint for the coop. I couldn't buy a ticket online or over the phone, and got the cellphone number of one of the guys traveling with the airplane. Which he didn't answer. I went to work on the coop, checking my phone every few minutes. When the girls returned from shopping, I dragged everyone to the airport. Cash was exchanged for a ticket on the Sunday morning flight, and we all got to walk through the bomber. I tried to explain to my kids everything that my dad had taught me, hoping to give them a feel for something that was already a couple of generations removed from me.

Dashboard Brother

April 28th, 2011

"TomTom admits to sending your routes and speed information to the police".

Well, if I'm ever in the market for a GPS, no way in Hell I'm buying from them. Sure it's a sensationalist headline, but the underlying information is that TomTom will hand out data about you to whomever they see fit. No thanks!

Securerer

April 27th, 2011

I finally changed the security protocol of our home wireless network over to WPA2. I have known that I should do so for years, but of course changing every device on the network would have taken like twenty minutes of work, and I am, in fact, that lazy. So we've been using WEP because, well, when I got the router set up initially its UI was so impenetrable that I was fooled into believing it only knew about WEP.

But the other day I was reading about the police breaking down someone's door because their neighbor was downloading society's current "worst possible material ever" via the hapless individual's unsecured wireless network. And I had just read about a firefox plugin that snoops on wireless traffic, so finally I checked up on exactly how easy it is to crack WEP, and that was enough.

Twenty minutes later, the laptops and the Wii are all happily running with WPA2. And I'm back to having only the government reading my network traffic.

Snap!

April 26th, 2011

Yesterday evening I was out on the deck putting meat on the grill. The boys were running around in the backyard; I had just leaned over to check on them before I started to put the meat on.

Then E. started screaming.

As my wife points out, E. has only one volume setting: screaming could mean he got a splinter, or it could mean that there is an alligator on his leg. Nonetheless, it sounded serious, so I called K. out to help him while I turned off the grill and dealt with the raw meat.

She ran out and down the stairs; as soon as she saw him lying on the ground she could tell it was serious. His right wrist was folded unnaturally; his right arm below the elbow had taken the shape of a lightning bolt.

She carried him inside as I called 911. The Vienna Fire & Rescue ambulances arrived in a couple of minutes, while we packed a bag with snacks and books. I rode in the back with E. as the paramedics tried with mixed success to cajole him. Luckily B. was not working that evening, so she raced home (on the bike) to babysit the little one, allowing K. to drive to the hospital.

It was a bad but clean break. They gave E. some pain medication, then hooked up an IV (which was, I think, the most traumatic part of the hospital visit). We did some X-rays, saw the bones (yeek), and they lined up the procedure. There was some stress when Dr. Lo came by to discuss the risks of the sedative they'd be using but K. was out front calling relatives; when she came back, he had gone, and we couldn't find him for twenty minutes. But eventually we got the low down and signed off on the anesthetic.

Then we changed rooms, E. got knocked out (which his body resisted mightily, demanding extra sedative and then coming back around well in advance of schedule) and K. and I left the room while the orthopedic resident reset the bones. We returned to find E. wearing a splint and the sedative already wearing off, leading to some interesting observations from E. about how how odd it was that we all had four eyes.

E. broke his arm at about 6:45 pm. We got to the hospital a while after 7; and we got home at about midnight. This morning there was some discomfort but after a little Tylenol 3 the boy seems to be fine.

Not what we had planned for last evening - and it's certainly going to put interesting crimps in the next couple of months - but all's well that ends well, I suppose.