2 ms·
Here's a good summary from Reddit: https://old.reddit.com/r/cscareerquestions/comments/b4jp0k/what_are_some_worthy_job_specializations_to_get/ej7cfuw/ https://o
by acconrad 8y ago
Here's a good summary from Reddit: https://old.reddit.com/r/cscareerquestions/comments/b4jp0k/what_are_some_worthy_job_specializations_to_get/ej7cfuw/ https://old.reddit.com/r/cscareerquestions/comments/b4jp0k/w...
As someone who has a CS background who wanted to work in front-end, I think a big portion of the "looked down upon" piece comes from an older era where front-end just meant HTML and CSS. Since there isn't much logic to HTML or CSS, it was looked down upon as easy from people with a CS background who generally gravitate towards the backend.
Now that the front-end is more robust with arguably just as much logic on the front-end, the thought is shifting. In addition, some people just don't like handling the GUI layer. For the back-end, dealing with the GUI layer is their least favorite part. So if you have a CS degree and you want to tackle the front-end, you could be one of the rare few who has the technical chops to handle this new world of front-end complexity.
- andrei_says_ 8y ago> there isn’t much logic to css and html well structured css and html are extremely important to project maintainability long term. Css is a declarative programming language and not at all trivial. As for JS based front ends, yes, they approach the complexity of game development and totally deserve due respect. As someone who has worked on both front end and back end code, I have a lot of respect for both. That being said, when I delegate work, I feel a bit more nervous about the front end because of the brittleness and potential compatibility issues.