10 Reasons Why Developers do not Make Good Hardware Administrators

Early this year, we had a power spike at our house during a wind storm...the net result, our home computer became unstable. Here are 10 reasons why developers don't make good hardware administrators:

1. Can't tell if the root drive failed
2. Can't tell if the power supply failed
3. Get lucky flashing bios first time
4. Get unlucky trying to flash bios second time (note, it's not good for your machine to power off during a flash).
5. Purchase new main board because first main board got fried during the bios flash
6. Tries fitting an ATX power supply into a MicroATX case
7. When putting full size ATX power supply into MicroATX case, the optical drive (7 3/4" long) will often not fit together, i.e., can't stuff an elephant in a 32oz jar of peanut butter
8. Tries fitting a MicroATX power supply only to find out it pushes the CPU core temperature over 150 degrees within 2 minutes of turning on (still can't figure out why this happened).
9. Refuses to contact technical support (this might be more of my own fault, I'm a bit thick headed).
10. Software Makes Sense!

---------------
Update: Apparently some of the Geek Squad corporate manuals have been leaked. One of which is their trouble shooting guide, what they use when you bring your broken computer into BestBuy. I could have used this earlier.