danjaouen

Living outside of the Bay Area has consequences as well. For example, I'm an out-of-work developer currently living outside of SF, and I can therefore only really apply to positions that allow for remote work (which are much rarer than HN would have you believe).

To me, the most important distinction between a "junior" and a "senior" developer is that a senior developer isn't afraid to work with and maintain legacy code.

When I first started out, I was obsessed with only using the latest and greatest technologies, but I've come to realize over the course of my career that this is simply infeasible for many organizations.

I have to disagree with the last part of your post. Some languages are actually better in quantifiable ways; for example, shorter development time, better performance, etc.

I've experimented with Chicago Boss a bit; it's an excellent framework, but I feel it still has a ways to go before it can compete with Rails.

I would pay a lot for a Rails-like framework written in Erlang. Erlang really hits a sweet spot between performance and developer-friendliness.