|
|
|
|
|
by solardev
959 days ago
|
|
Today, I think it's also possible to work in higher levels and not need to know the ins and outs of CSS as much anymore. They're more "nice-to-haves" rather than "must-haves", and you can usually Google/StackOverflow your way out of rabbit holes as you encounter them, not needing to learn all of it at once beforehand. I'm a frontend dev who grew up with CSS, but some of my coworkers started after that era and still contribute valuable work. A lot of it is in higher levels of abstraction now, such as component libraries (whether built in-house or third-party or, often, a forked/extended version of an open-source one). The CSS is already mostly defined for you by these systems and for the most part they're fine. Yes, your UIs end up looking a bit generic, like the modern version of "just another Bootstrap page", but I'd argue this is a good thing: that FE devs can now spend time building business logic and user flows instead of (sigh) centering divs across three browsers. |
|