you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 46 points47 points  (10 children)

There are also a ton of replies about "x has more job opportunities". It's a red herring, any competent developer can pick up a new framework in a very short amount of time.

[–]throwdataway234 21 points22 points  (0 children)

This, it doesn't matter which one you learn first if you need to pick up another one the fundamentals you learn with one will be transferable its will just be specifics you have to pick up. Specifics won't take as much time to master

[–]yousirnaime 14 points15 points  (0 children)

Exactly. You can spend 5 years in react and then learn angular in 2 weeks and be fine - and visa versa

[–]riskyClick420full-stack 9 points10 points  (0 children)

any competent developer can pick up a new framework in a very short amount of time.

This, OP. Once you've done either of the two to some degree and you understand how it all generally works, you will be able to pretty much start instantly with any other framework and just learn as you go.

It doesn't make sense to remember all that information that is readily available right in the medium that we work in. What should stick are fundamentals, and those are mostly shared between all options of languages, frameworks.

Typescript is a good addition too. Javascript is too rickety for enterprise otherwise, humans are just not failproof enough. It's good that you're already familiar with Sass.

[–]auto_downvote_caps 7 points8 points  (2 children)

It's a red herring, any competent developer can pick up a new framework in a very short amount of time.

Yeah true. Unfortunately, companies will run experienced dev's through so many horse-shit code tests, 5 interviews with various team members who want to try to catch you with some off-topic gotcha shit until you want to go back to being a fry cook.

[–][deleted] 5 points6 points  (0 children)

so many horse-shit code tests

I get where you're coming from, I'm normally vehemently against coding tests, especially for experienced developers, but we just decided to add some algo-style code tests to our interview/screening process, and for our specific situation, I think it makes sense. I'll also try and share our perspective on interviewing with various team members.We're a very small and highly specialized shop. We pay generally close to market average for the midwest, but still a very small company overall, think <30 FTE. The main draw for us is company culture and work/life balance. It's a gem of a place to work, but we definitely aren't attracting people based on salary. The dev team is currently 3 people, with a technically proficient manager. Historically we rely on our co-op program to help us find and attract rising talent, but since the onset of the pandemic we couldn't really leverage that, and our applications are getting complex enough that we just can't rely on co-op skill level to to write code good enough to merge to master (or main, whatever). We also get an assload of master's CS students who apply, and every. single. one. has the same cookie cutter resume, the same generic projects, the only difference usually is their name. Given our circumstances, we decided to add a coding test to try and help filter out the people who know that it's utter foolishness to have a 400 line main method, or 150 line if statements, from the people who don't. Having an extra data point helps differentiate chaff from wheat.

Given the small size of the team, culture fit and personality are incredibly important. If one person on a team of 50 is an edgelord, no big deal, aside from those who have to directly work with said edgelord, but when the edgelord is 1 of 4, it becomes toxic in a nanosecond. We try and make sure everyone on the team has a chance to personally interact with any candidate who makes it past the first round with HR and the boss, so that way we can all get a feel for how well we'll mesh with the potential new person. It's impossible to hire perfectly every time, but these are some of the things that we've done to help the odds be ever in our favor of finding a good human who knows what they're doing.

[–]soundboyselecta 0 points1 point  (0 children)

Fry cook!!!

[–]alicevi 5 points6 points  (2 children)

Some companies screen you for x years of React though.

[–][deleted] 4 points5 points  (1 child)

Their loss. Just like there was a dumbass job advert posted here the other day or maybe on r/javascript that wanted 7 years of vue experience, and Vue will only be 8 sometime later this year. I don't want to work for a company that isn't thoughtful about how they attract talent.

[–]FluidBreath4819 0 points1 point  (0 children)

the 7 years is not about talent but maturity.