I’m Kenigbolo Meya Stephen, Senior Full Stack Software Engineer working as the Frontend Engineering Lead at BCaster. Arch Conveyer/Community Manager of CodeAfrique, a not-for-profit weekend intensive software engineering Bootcamp for underrepresented groups in tech. I’m also a member of the Node.js package maintenance team as well as a writer for Ultimate Courses (@tryultimate)
During my free time, I sometimes volunteer as an open-source developer for https://adsbexchange.com, sometimes play golf and other time play or coach football (soccer as Americans call it).
More often than not developers fall into the trap of wanting to use some shinny trend heard in the IT world and that is no different with web components. Do you really understand the design decisions behind the concept of web components? In this talk, we’ll take a deep dive into what it is all about.
In the last few years, the term web components have become a main stay in frontend development and web development at large. This popularity as usual tends to come with a huge adoption in the industry albeit without people actually understanding the core concepts behind this new frenzy they’ve encountered. This isn’t limited to juniors alone. The goal of this talk is to give a deep dive into the background behind components, where it came from, how it has evolved and possibly what we might see in the future.
As a software engineer who volunteers as a teacher in a free self run coding school together with my peers, more often than not, a question we get from curious students and young developers are “why is this or that being used”. Giving answers like “it is used for this or that” has over the past year proved to be counter productive for trainees and engineers alike. With the last cohort of Code Afrique, we decided to take a different approach in explaining the concepts of web components by explaining the evolvement of web components from how Microsoft HTML Components and Mozilla XBL tried and failed and then Angular picked up by using the lessons learned from the failure to introduce what we now know as modern web components via a better semantic on web apps that allowed developers to create their own tags and how react further evolved it by fulfilling the need of reusable widgets. This we have seen has helped the developers and trainees have a better understanding of the concept of components on the web.