This old saying (as do many others) still rings true today and I imagine it always will be relevant. Most people are never fully satisfied with their own situation, and always think others have it better. Sometimes it is true, other times it is not, and sometimes it is just an argument of semantics. If you let it, this thought process can lead you to a depressed state or it can light a fire under your ass and push you forward. It’s a fine line to walk.
While reading an article and some of the user comments today, a commenter offered a few words to another responder that helped put my professional thinking back into a more positive perspective.
You are effective at all levels of the stack, and can build entire webapps (given enough time) by yourself, and you’re complaining about it?
The reason this little response hit so close to home is because I’ve grown into the “jack of all trades” role. I didn’t start out there, I was a “master at one” with a few other skills that were required and hard to find. I was worried about loosening the strangle-hold grip I had on my main skill-set. I thought my “master” level of ability would disappear and I would be left with a bunch of knowledge across a wide array of skills, and not really mastering any of them.
Though this can lead to a career killer, it didn’t for me. I’m able to stay relevant, I’ve learned so much more than I ever would have and it helps me to bring many different assets to the table that prove to be very beneficial to all involved. However, I do still try to concentrate on certain aspects of my skill-sets so I can say I am a master of at least one. And that quote above helps me to stay positive, something that is hard to do in today’s world, yet is so crucial.
I like to creep my wife out every now and again by playing some Q Lazzarus – Goodbye Horses and talking in that fucked up retarded voice Ted Levine has. I’d recite a few lines from the movie The Silence of the Lambs, I’d have a chuckle while my wife shivered and that would be that.
Well today, while listening to some Oingo Boingo – for some reason – that song popped into my head and I wanted to find out just exactly who Q Lazzarus was. That’s when I got a surprise myself. If any of you are familiar with the song, and/or the movie The Silence of the Lambs, it fit too perfectly. I honestly thought that was a dude singing the song. Nope, it’s not. It was a chick with a husky voice! Holy shit-balls! I had no idea and never would’ve guessed.
Honestly, I still kinda like the song because it reminds me of the movie I attribute it to, though it’s been used in other movies. And I still like creeping my wife out at times. But to actually look this up and find out a bit of what’s behind the song actually made me feel a bit creepy myself. Whatever, I’ll still always like to tell my wife to “put the lotion in the fucking basket” and such. I haven’t perfected that insane, semi-retarded, cleft pallet, talk in that occasion for nothing!
Here’s a real video for Goodbye Horses:
And here’s a song and video by The Greenskeepers, inspired by the movie and song, that I thought was very well done:
Now that’s some serious camouflage. Side note: I knew I was going to spell camouflage partially incorrect, funny part was Firefox giving the spelling suggestions, one of them was guacamole! Jesus christ, I wasn’t that far off!
John does an alright job at explaining today’s functionality issues across various browsers and platforms. Earlier in my career, I had a very hard time explaining how complex of an issue this actually was and convincing people that there needed to be a line drawn in the sand. If no line was drawn, I would be forced to use old methods and in the rare case not be able to provide the intended functionality across all platforms and browsers. I’ve had many confrontations with team members as to why I chose a certain method for implementation while they had no clue of the numerous pitfalls and necessity for my implementation to reach such a wide a varying market of browsers and platforms.
For example, in 1995 I had to support just about every known browser and platform – no matter how slim of a market share they had or how far out of our demographic they were. Doing that caused me to bloat the code by probably 50% in some cases and still experience a few small issues in some of the less common browser markets.
Even back then, we looked toward the future where browsers would become more and more standards compliant and relatively use the same, or near the same, set of rules or standards. While advancements have been made towards that goal, almost every browser still has proprietary implementations that do not follow a strict guideline. This makes for a hard time when trying to code / script with new technologies and still meeting old requirements. User experience and performance are typically the two that probably suffer from it the most.