5 ms·
> What are some need to know things in terms of frameworks and workflow that I should be aware of? Strange times, isn't it? 10 years ago, a front end job would
by camus2 10y ago
> What are some need to know things in terms of frameworks and workflow that I should be aware of?
Strange times, isn't it? 10 years ago, a front end job would require a comprehensive understanding of CSS, the DOM and JS. Now it's all about framework X and Z, build tool A or B, Typescript and what not, like these tools are so complex one has to be a specialist in these tools because they can't be learn in a few days.
Meanwhile, micro-services are all at rage on the server and back-end developers deemed big frameworks like Rails,Spring,Symfony and co an anti-pattern because complexity is bad (Go)? But stupidly complex tools and frameworks on the client are OK?
- Stoids 10y agoIndeed, it's almost as if web application expectations and requirements have gotten significantly more complex in 10 years time. Microservices don't reduce technical complexity. If anything they add to it. 10 years ago I didn't have to worry about container orchestration and all that comes with that. New problems present new solutions. I definitely recognize that the transpilation era of JavaScript feels incredibly bloated. It is exacerbated by the overlap with a lot of the tooling. It's exponentially worse when you try to understand solutions to problems you don't have yet.
- gt2 10y agoIn your opinion, what are a few "new problems" that require the new solutions like microservices and container orchestration?