desjardins
Superstar
@craz_eddy
disclaimer: this is just my opinion and based on my own anecdotal experiences
unless you work for Google/Facebook/Amazon/Netflix or somewhere on that level I think a young developer should be looking to job hop every 2 years or so. As long as you are learning new things and taking on increasing challenges I don't think anyone will look down on a developer moving around that much. Just be able to explain why you felt you had to bounce. It rarely comes up when I interview but I usually just say I'm looking for a more challenging position. Once you get more senior this could change as you should begin to develop greater domain expertise. But before 30? Def job hop.
Job hopping is the easiest way to get pay increases and it can expose you to a lot of different tech stacks. For example I've used almost every version control (svn, mercurial, git) , developed on both Oracle and Sql Server, done waterfall/agile/and TDD, and have used ant/maven/and gradle build scripts on command line and Jenkins automated builds I set up. That's just in the last 4 yrs worth of jobs.. If I stayed at the same place I wouldn't have all those experiences and couldn't put them on my resume or speak to them from a real world production perspective etc
Only way I see job hopping being a bad look is if you are only staying at places for like 3-4 months. Or if you are job hopping to avoid getting fired (I worked with dudes who did this and caked but it will only last so long)
As far as github and outside projects....i don't have any worth sharing, only lil tutorials and stuff like that are on my github. I'm too busy working. It's 9pm east coast time and i'm about to build some apache camel routes for an integration project i'm working on right now. this is for research purposes and i could put it on github i guess but i'm not pressed. as you can tell from this reply i work mainly in enterprisey stacks. hiring managers who contact me are mainly looking for real world experience and interview competence for the most part. but it could be much different on the west coast in the start up space i imagine or if you don't have that much real world experience. (also it's possible hiring managers are tossing my resume in the trash because i don't have a github url on it.....but i can't tell judging by the amount of interest i get when i'm on the market)
disclaimer: this is just my opinion and based on my own anecdotal experiences
unless you work for Google/Facebook/Amazon/Netflix or somewhere on that level I think a young developer should be looking to job hop every 2 years or so. As long as you are learning new things and taking on increasing challenges I don't think anyone will look down on a developer moving around that much. Just be able to explain why you felt you had to bounce. It rarely comes up when I interview but I usually just say I'm looking for a more challenging position. Once you get more senior this could change as you should begin to develop greater domain expertise. But before 30? Def job hop.
Job hopping is the easiest way to get pay increases and it can expose you to a lot of different tech stacks. For example I've used almost every version control (svn, mercurial, git) , developed on both Oracle and Sql Server, done waterfall/agile/and TDD, and have used ant/maven/and gradle build scripts on command line and Jenkins automated builds I set up. That's just in the last 4 yrs worth of jobs.. If I stayed at the same place I wouldn't have all those experiences and couldn't put them on my resume or speak to them from a real world production perspective etc
Only way I see job hopping being a bad look is if you are only staying at places for like 3-4 months. Or if you are job hopping to avoid getting fired (I worked with dudes who did this and caked but it will only last so long)
As far as github and outside projects....i don't have any worth sharing, only lil tutorials and stuff like that are on my github. I'm too busy working. It's 9pm east coast time and i'm about to build some apache camel routes for an integration project i'm working on right now. this is for research purposes and i could put it on github i guess but i'm not pressed. as you can tell from this reply i work mainly in enterprisey stacks. hiring managers who contact me are mainly looking for real world experience and interview competence for the most part. but it could be much different on the west coast in the start up space i imagine or if you don't have that much real world experience. (also it's possible hiring managers are tossing my resume in the trash because i don't have a github url on it.....but i can't tell judging by the amount of interest i get when i'm on the market)