3 ms·
I have a very similar career trajectory, but starting a few years earlier. Remember web rings? Anyway I think there were two phases of the complicated web: -
by eyelidlessness 6y ago
I have a very similar career trajectory, but starting a few years earlier. Remember web rings?
Anyway I think there were two phases of the complicated web:
- there are build tools emerging (grunt, gulp, etc) and now web apps have a build step to automate certain complexities like minification, but you write more or less plain HTML/CSS/JS or maybe transpile if you prefer.
- the build tools are your entire process and the languages you write in are constructed by an infinitely configurable set of inscrutable plugins.
I didn’t intentionally shift toward backend, but it did happen gradually between those two phases. Having spent the last few months getting reacquainted with frontend, the phases feel very distinct. I know HTML, I’ve gotten caught up on CSS. I’m perfectly comfortable with React and I love JSX for the most part. But I spend most of my time appeasing/fighting with tooling.
Even though I’m writing in the same language (TypeScript) that I’ve used for years and feel very comfortable with on Node, all the frontend types feel like a funhouse mirror reflection of the language I know. I’ve lost entire days just trying to satisfy types on a HOC.
I’m not giving up because I’m excited about my project but I can honestly understand the author’s feelings. I sincerely don’t think it has to be this difficult. And I can’t imagine being new to programming walking up to the current frontend process.