I have two job offers, both with almost exactly the same pay and location. The first job is in a new tech stack and different industry/domain: Java, aws, kafka etc. The second job is with almost exactly the same stack (python, gcp) and even the same work and industry as current team at spotify. i’m conflicted because I’d like to learn new things and my professional experience has only been in python, i think Java would be great to get experience in for future opportunities. However, the people i’ve met at company 2 are all fantastic, I feel like I’d get along really well with the team. Not saying company 1 is bad but i don’t have the same feeling with the team mates there. tc: 80k europoor
Spot on. As long as you don’t join startups, they likely will not care what tech stack you have experience with or not. Learning new language and stack is all factored into onboarding.
Tech Industry
Yesterday
8812
China CYBERATTACK on UK ? WTF
Tech Industry
9h
1867
Are tech workers as rich as they think we are?
Tech Industry
7h
1283
How can my idiot brother who does real estate afford this
Today I Learned
Yesterday
1143
My understanding of the Holocaust was incorrect!
Health & Wellness
Yesterday
2467
I hate my f***** life
Why do you care about _how_ things get built instead of _what_ gets built? Python vs Java is not what’s going to define your career and both are plenty widespread, generic stacks. A good technologist should be able to pick up either. Choose the projects/industry that interests you and coworkers you can level up with and like being around. Unless you are working on something incredibly niche and specific, no one cares whether you know Python or Java or aws or gcp they expect you to be able to adapt and provide value.
the main appeal for java to me is learning solid OOP principles. i don’t have a traditional cs background so i am weak in this area, thought it would benificial
1. You do that BEFORE you join a Java shop. Even the people who say language doesn’t matter assume you’re competent enough to learn quickly (and they have probably studied OOP at least once in college or wherever). If you don’t know how OOP works at all, you’re setting yourself up for failure. 2. @ the commenter, the advice you’re giving is not grounded in reality. Ideally, it shouldn’t matter. In reality, these things often derermine who gets through the door. Not everyone (especially recruiters) think in engineering ideals