[liquidcool]

I see some common ground between us. I, too, got roped into being a generalist early. After 15 years it's an advantage (you can call yourself a consultant), but can be trying before that.

I suggest you pick the stack you enjoy the most, pick a project that gets you excited, and stop learning new things until you've mastered one (well, one set).

If you're not sure which that is yet, pick a newer technology that no one can claim deep experience in. I've seen people get involved in projects early on, start blogging and talking about it, and next thing they're being flown around the world to present at conferences with a good stream of consulting income. Pretty sweet gig. Does require excellent communication skills, but they can be learned and pay off forever.

When I read that you are using analytics to make improvements, I see an opportunity missed: quantify your impact in dollars. Engineers are usually bad at this, but managers are good (assuming a top down push for metrics, which is common), so talk to yours and find out how you're earning your keep. Then put that on the resume and see how it helps things.

[taurenk]

I have found myself jumping from technology to technology, which is something I'm trying to do less of, for example; I started a project in Python then when it was pretty much finished started to re-write in Java for numerous reasons (learning java being the key driver).

What you said makes sense and definitely has me thinking about things a bit differently. Thanks!