Now @marimiyachi and @samskeller are talking about building their own ORM (object-relational mapping) at work— why they did it and the challenges and benefits of doing so 🕸 #EmpireJS
Seams... like @Tracidini’s legacy this year is talking about how to deal with legacy code: find the seams, find bridges between libraries, and finally the rewrite! 💿 #EmpireJS
.@thathijabae just mapped out the problems with getting population data for migrant communities (1000 line spreadsheets!) and how she learned to use d3 to visualize it 🌏 #empirejs
And now @nitya is shedding light on Google’s Project Lighthouse— what the audits mean and what to do with the information... by auditing the EmpireJS website! 🔦 #EmpireJS
Last talk before lunch period! @sitnikcode is showing us how to build the most quintessential of demo apps, a todo app, by using a CRDT (conflict-free replicated data type) ☑️ #empirejs
Now @Snugug is sliding through his slides on slides, explaining how to create a performant progressive web application using his slide-making project as an example 📽 #empirejs
We learned so much from @maninilchiani’s talk on his journey to try to port his work on Diffy.js to WASM (including but not limited to what is wasm anyway?) 💫 #empirejs
Thank you so much to @empirejs for having me out to talk about the history of tech workers’ organizing. For those curious I’ve made my slide deck public here docs.google.com/presentation…
We’re all fired up from the points @ughitsaaron raised about the legacy of tech and tech workers participating in and resisting injustice in their companies, communities, and beyond 💪🏼 #empirejs
Now @kadamwhite is im-pressing us with his words on how WordPress adopted JavaScript in their Project Gutenberg, taking into account the needs of their developer base 🗞 #empirejs
Kicking us off for day 2, we have @KellySutton bringing us back to history class with a lesson on how web development came to be what it is today, from programming computers of the 70s to the advent of JavaScript to Webpack 🔜 #empirejs