3 ms·
> just feels like there's this overwhelming amount of constant change and detail The good news is, you can mostly ignore it. I have 20 year old server-side ren
by naasking 3y ago
> just feels like there's this overwhelming amount of constant change and detail
The good news is, you can mostly ignore it. I have 20 year old server-side rendered apps that are still running just fine today. Why run on that treadmill? Find something that looks solid and makes sense, and stick with it for awhile.
- DavidPiper 3y ago> The good news is, you can mostly ignore it. Not if you work in shared codebases with other teams who don't ignore it. But otherwise: > Find something that looks solid and makes sense, and stick with it for awhile. 100% yes.
- danielvaughn 3y agoFor my own tech yes, I can ignore it. But for job opportunities, the unfortunate reality is that recruiters, hiring managers, and interviewers will be looking for knowledge about relevant tech. I don't want to learn NextJS, and you will not catch me trying to use it in my free time. But if one day I apply for a job that's looking for people with knowledge of NextJS, I probably won't get that job. And if it comes to pass that the majority of the industry moves to NextJS, I'm now at significant risk. Of course, when I hire I look for fundamental skills, not familiarity with XYZ technology. But I've seen people hire that way, and I know it's fairly common in our field.
- naasking 3y ago> And if it comes to pass that the majority of the industry moves to NextJS, I'm now at significant risk. I think "significant" is overstating it. Learning new tech is not that hard, particularly if you're already familiar with adjacent tech. I recognize that some people look for checkmarks on a CV, but if that's how they operate then you probably don't want to work there.