Explore >> Select a destination
|
You are here 
|
adactio.com | ||
| | | | |
www.fullstackacademy.com
|
|
| | | | | Confused about the differences between a software engineer vs. software developer? Take a look at the engineering training required and scope of the job | |
| | | | |
designsystems.wtf
|
|
| | | | | The importance of reviewing expectations and providing small incremental ways to adopt your design system | |
| | | | |
lamplightdev.com
|
|
| | | | | Chris Haynes - web developer consultant | |
| | | | |
lea.verou.me
|
|
| | | Disclaimer: This post expresses my opinions, which do not necessarily reflect consensus by the whole Web Components community. A blog post by Ryan Carniato titled "Web Components Are Not the Future" has recently stirred a lot of controversy. A few other JS framework authors pitched in, expressing frustration and disillusionment around Web Components. Some Web Components folks wrote rebuttals, while others repeatedly tried to get to the bottom of the issues, so they could be addressed in the future. When you are on the receiving end of such an onslaught, the initial reaction is to feel threatened and become defensive. However, these kinds of posts can often end up shaking things up and pushing a technology forwards in the end. I have some personal experience:... | ||
