4 ms·
Thank god I have a specialization that allows me to not have to follow the framework crap. I could care less about staying up to date with some dude's opinionat
by iamleppert 8y ago
Thank god I have a specialization that allows me to not have to follow the framework crap. I could care less about staying up to date with some dude's opinionated way of doing things. It has not affected me getting a job, because when I go to get a job I work in an industry where my domain expertise is valued much higher than the fact I like framework X or happen to have used it or forced myself to read some book on it.
I feel sorry for people who all they have is that going for them, it's a rough like constantly keeping up and re-learning the same MVC or UI lipstick every year. If you call yourself a React programmer, you're the next PHP Symfony Programmer or "Rails Developer". It's a completely different kind of engineer, kind of like the difference between someone who does IT but can't code. I cringe and immediately avoid any companies who advertise for "React Engineers" and the like.
I realize that some developers couldn't care less about what they are actually working, the product behind the code but I'm not one of them.
- kjeetgill 8y agoI think that's a little pessimistic (and a shade condescending?). You can easily call yourself a React Engineer today, for one interview, and be a frontend specialist for the next. If your company is using a stack, why wouldn't you hire people that actually like to work with it and know its quirks? As someone who mostly does Java infrastructure work, sure anyone can learn Java. It's the easiest. But there's plenty of room to bring value with experience and specialization if you want. I just hope no one feels forced into it because of market forces.