Full-stack developers have a lot to deal with these days: CSS frameworks, frontend MVCs, REST servers, databases, and more. That not including any infrastructure, containerization, and additional operations work. The three end states for full-stack devs are trying to do everything themselves (resulting in poor quality across the board), working endlessly (ending in burnout), or compromising on overall control of everything and augmenting their skills with frameworks and tools. This talk discusses how to best come to terms with relinquishing control and finding good frameworks when it comes to frontend development.
I'm a full-stack developer who adopted frontend development out of necessity. I normally work with a Java stack, though I've worked in many other languages as any developer will. Most of my experience is in rapid application development spanning from infrastructure to UI. My hobbies include drinking coffee and finding new open-source projects.