BLOG: Mitch Wilson, Austin TX Web & Multimedia Developer – Austin, TX

WRX in parking garage

Today I parked next to a 2011 Subaru WRX in the parking garage. It was white and looked great. Much better than in the pics on the Subaru site. The nose was not as long.

git help: checkout new clean project copy

I love git. But throwing away changes you've already committed locally can be a real pain. A git guru buddy of mine ("Thanks, Mike!") provided a command line incantation worthy of sharing, since this is such a common problem frustrating git lovers around the world.

WARNING: this procedure deletes all files in the branch (project), even files not checked in. So you must first move all unchecked files to another directory.

From the command line (my example is on a mac) in your git repo root directory:

1. Run git status. The output will list any "Untracked files" .
2. Move all "Untracked files" you want to keep to another directory for safe keeping.
3. Run git status again for review before running the following destructive procedure.
4. Run these commands.
   git checkout -f
   git clean -f -d
   git reset HEAD^^^ --hard
   git checkout -f
   git clean -f -d
   git pull

Wow I have a youtube channel

You probably do too. I mean, I did and didn't even think about it until now. What great tech times we live in. I have a whole videos site just by marking favorite videos.

Check it out, if you dare.

Validate your damn code, please

Sorry, I have to rant. I'm working at 4am and marveling at the code mess big-ball-of-mud thing before me.

Designers, developers, our bosses and loved ones like to complain about browser inconsistencies. Often my four-year old says, "Daddy, why doesn't my CSS work in IE8?" This is kitchen-table discussion-material across America along with religion and taxes. You have your zealots, like me, and then you have the "Hey I just need to get this code finished, ok, I'm going to hack this page with whatever I google." Face it; we've all done it. Now we need to stop. Or stop bitching. My four-year old can get away with it. He won't learn how to validate until he's five. What's your excuse?

Here's mine. Validate the home page of this blog. I just did. 20 errors and 20 warnings. Unfortunately when you try it might not work, because my blog redirects. Oh the happiness and hypocrisy. Yes. But it's not me. It's them. Those people who give me WordPress widgets, for free -- thank you! So my blog is an exception. Everybody has them.

Everyone also has projects that should not be exceptions. Like work projects. Like projects you charge people for and then depend on. And the people, teammates, co-workers, friends, and loved ones who work on the code after you depend on things like Web standards and valid well-designed code.

You of course are the first beneficiary. If you're asking, "Why doesn't this work in IE!?!" Ask yourself, "Is my code valid? Do I use a doctype?" If either answer is "No" or "What?" then you have a problem. It's time for an intervention. Help me help you. Listen. Commit. Validate your code.

Or stop bitching about browser incompatilibites and just say, "I"m a tool and part of the problem."

How can you even expect different browsers to render your page the exact same way ... if your code is invalid? So you get a pass but browser makers don't?

I don't think so.