[uberPhil]

I personally don't like the idea of "levels", especially with programming. IMO it adds to the "I'm better then you cause I do xyz code" mindset which seems to get adopted more and more each day. It actually almost turns me off and makes me not want to participate in the community.

Perhaps that mindset is more common among those in the valley or other tech "hot" areas. But around here, Washington DC, if you know People Soft and SharePoint you can easily command a salary ~130k salary. Knowing how to write your own Ruby implementation or js library gets you pretty much nowhere.

/end My first HN comment :)

[brildum]

If you increase your skill/knowledge that doesn't hinder your ability to use PeopleSoft/SharePoint. It certainly expands your options. While you can get a good salary using those technologies, eventually they will be obsolete. When that happens, we'll start to see news stories posted on some future-HN about how older IT workers are being passed up for younger, fresher IT workers and how it is a biased industry. When in fact, its just a group of people who decided that sitting in their comfort zone doing their day-to-day was good enough and when it was time to move on, they couldn't find any other jobs that fit their particular niche they'd had for the last decade(s).

[uberPhil]

Or it could just be that the younger crowd is using the tech that is popular today, therefore they are in higher demand.

10 years from now some next best thing will replace Ruby and the cycle continues..

As in my original post, the issue I have is the concept of knowing how to write your own language being considered a HIGHER skill then someone knowing Sharepoint or visual basic in depth.

Who's right is it to say that my particular skill is better or higher then yours..

[brildum]

Knowing how hardware works, how languages are compiled/designed, how libraries are architected. It can only increase your knowledge of [insert technology here].

I think you're confusing "Levels" with A > B (A is better than B) when in reality the point is that: A comes after B. You must first understand B, then you can move on to the next level in your path of understanding programming.

[steve8918]

Actually I've found that in Silicon Valley, no one cares about quantifying programming levels, and care more about what you did and what you know.

When I applied for jobs on the East Coast, they all seemed to want things like GPA (even though I'd been out of school for 15+ years), and especially results from programming tests like Brainbench.

[Maro]

So you're saying that Washington DC and Silicon Valley are different bubbles.

@uberPhil: I'm in Hungary, so I'm not a bubble boy =)

[uberPhil]

Pretty much.. But my bubble is better then your bubble! :).

FWIW I am a "programmer".

This list also doesn't take necessity into account. Is "A" programmer better then "B" programmer if "B" programmer has never had to derive their own programming language while "A" programmer had this requirement or need?

This entire concept is just silly to me.