Glad to see I am on the right track and that others have had success managing their career path. Thanks for all the great advice!
Moral of the thread: Never stop learning!
71–80 of 97 posts
Glad to see I am on the right track and that others have had success managing their career path. Thanks for all the great advice!
Moral of the thread: Never stop learning!
You can also try some contract work/start own business and do some simply projects that one-man-band can handle - I was trying that too and after every project I've felt that my skills got a boost.
Best,
ł.
Earlier quoted context omitted.
This! I've had the opportunity to hire for our company for the past year or so. We use a somewhat uncommon paradigm in our tech stack that is very attractive to a lot of developers. Many of our applicants have exactly what you said: plenty of side projects in that paradigm / stack and participation to meetups / communities etc. Occasionally however I run into people who have absolutely no side projects and have been…
I agree that someone who doesn't have side projects isn't as attractive as someone who does, in general. But there are lots of people who don't do any programming once they leave the office (8-9 hours of computer time is more than enough for them). That doesn't mean that they aren't dedicated or that they are a risk. I think it should be a case by case basis.
I think if you want to switch, I think its more important to demonstrate skills in the base skill set (in my case software architecture), and then there are plenty of people willing to give you some room to grow.
I did this back in 2009. Here's how to do it. Pick a technology stack that you want to get a job in and build a side project in your spare time. Attend meetups with experts in your local community and learn how to make it awesome. Build relationships with them along the way. Use those relationships to get some part-time contract work in said technology stack with someone local. Document this experience and build up a…
This! I've had the opportunity to hire for our company for the past year or so. We use a somewhat uncommon paradigm in our tech stack that is very attractive to a lot of developers. Many of our applicants have exactly what you said: plenty of side projects in that paradigm / stack and participation to meetups / communities etc. Occasionally however I run into people who have absolutely no side projects and have been…
I can understand a false "expert" delusion, but have you literally heard someone say they'd never work on something unpaid because it's unprofessional?
Earlier quoted context omitted.
This! I've had the opportunity to hire for our company for the past year or so. We use a somewhat uncommon paradigm in our tech stack that is very attractive to a lot of developers. Many of our applicants have exactly what you said: plenty of side projects in that paradigm / stack and participation to meetups / communities etc. Occasionally however I run into people who have absolutely no side projects and have been…
> "I'd never work on something I'm not being paid for, I'm a serious professional that's irresponsible". I can understand a false "expert" delusion, but have you literally heard someone say they'd never work on something unpaid because it's unprofessional?
We don't care about what tech stack you know, we're willing to teach you ours. We just need you to be extremely motivated and ready to go!
Do companies really try to pigeonhole developers into "tech stacks" so much that you'll be forced to revert to junior status to change? Unless we're talking about COBOL -> Haskell here, I think any decent company would be wary of overvaluing skills with a particular language or framework and undervaluing fundamentals.
For example.
If you are a C# programmer who has never done Java programming. It takes you 6-12 months to get reasonably up to speed with the JVM, standard libraries and idiomatic coding. Let alone any dependency injection, web framework etc. libraries.
Why would the Java shop pay you the same as a developer who has spent the last 5 years doing Java full time who can be productive in Java right away?
That said, I think reverting someone to junior status is too extreme. A slightly lower salary or requiring an 'ace up your sleeve' to compensate is probably fair.
Earlier quoted context omitted.
This! I've had the opportunity to hire for our company for the past year or so. We use a somewhat uncommon paradigm in our tech stack that is very attractive to a lot of developers. Many of our applicants have exactly what you said: plenty of side projects in that paradigm / stack and participation to meetups / communities etc. Occasionally however I run into people who have absolutely no side projects and have been…
I agree that someone who doesn't have side projects isn't as attractive as someone who does, in general. But there are lots of people who don't do any programming once they leave the office (8-9 hours of computer time is more than enough for them). That doesn't mean that they aren't dedicated or that they are a risk. I think it should be a case by case basis.