Shave brush stand

The problem: How do you store your shaving brush between uses?

Water will gather at the base of the bristles and mold
The brush will deform and the bristles will curl over
both the 1sr and 2nd problems here

The Solution: A brush stand. There are some lovely commercial stands that I’m sure do a great job, and eventually I may buy or make a more beautiful solution, but for now, I work with what I have… Plastic covered steel wire.

Start with a big 'V' of wire and bend a small "ledge" into the point. Give yourself plenty of extra wire.
Finish bending in a depressed section. This part is pretty tricky and takes some trial and error. You want the "back" wide enough to be stable, but not so wide that it's hard to get to the next step
Bend some more, then add a little twist. I tries something more symmetrical, but this was the only way the thing was rigid enough to stay upright. if you want to add clamps or glue, you could probably sort out a different arrangement. This has actually grown on me now, though.
Test fit... adjust.
Test fit... adjust.
There you go... Stuff you probably have around the house and 30 minutes of messing around.

Of course, I’m not the first to attempt this. After (yes, after) making this, I came across this Instructable:

Not bad. I like the inclusion of the razor in the stand, but I prefer one that works with the cup. Wet brushes drip, and I’d rather have mine drip into the mug than onto the counter.

Note: Both the mug and the pliers belonged to my grandfather. The brush is a Tweezerman Deluxe shaving brush. It looks like the same one as in the linked Instructable, and I can say it is a good brush.

First post… again

rm -rf license plate
yeah... it always seems like a good idea...

Ok, so here’s what happened…

My sweet, sweet WordPress blog got hacked, which is bad. I’m not sure that it was actually my blog that caused the issue, but it was certainly affected. To my dismay, every visitor to my blog was getting prompted to download the lastest and greatest in 7 year old viruses. Rather than just being pissed about it, I decided to take it as an opportunity to clean house. I’d needed to clean out some old, aborted projects anyway, so I did what anyone with a passable knowledge of *nix system administration does… I broke out my trusty sledgehammer:

rm -rf

…and I went to work. I deleted temp files, and download directories, and “_old” directories. I killed all of the crap that was left over from trying to get RoR working. It was exhilarating! As I approached the /blog directory in an rm induced haze, I did that thing which we all dream of getting some n00b to do:

Hands: cd ~/blog

Brain: La, la, la…

Hands: rm -r

Brain: La, la l… er?

Hands: f *

Brain: ummm… maybe we should stop with the f?

Hands: [evil laugh] [ENTER]

Brain: Shit.

And that was that. The blog was gone, and the worst part was I still had that whole “my website is handing out viruses like Typhoid Mary in 1915 New York” thing to deal with!

Solving that was actually kinda fun. It turns out a bunch of nasty had been added to the beginning of a bunch of PHP files in a bunch of directories. Removing this crap one at a time would have been a serious PITA, so I did some research and came up with this little bugger:

find . -iname '*.php' | xargs grep -l -R -E "<\?php \/\*\*\/ eval\(base64_decode\(\"aWYoZnVuY3Rpb25fZX(.*)\)\);\?>" | xargs sed -i  's/<?php \/\*\*\/ eval(base64_decode(.*);?>//'

Sweet, right? You figure it out… I’m citing the following from Real Programmers Don’t Write Specs:

Real Programmers don’t comment their code. If it was hard to write, it should be hard to understand.

Thanks, and good day.