Taking place in Vancouver, British Columbia, Node+JS Interactive could not have chosen a better place with the ultimate panoramic view of the mountains and the harbor.
Some of the keynote highlights:
One of the first keynote speakers was April Wensel (founder of Compassionate Coding), who talked about the prevailing stereotype of developers being sedentary, sleep-deprived, and antisocial. She explained how the culture has developed around this harmful stereotype which leads to unbalanced and ineffective teams, destructive behavior in our communities, and the high incidence of burnout among developers. In her talk, she invited us to care more about the people in our lives and to become more compassionate with our behaviour.
“Software may be built on machines, but it’s built by and for human beings. If we want to create more useful software and enjoy more sustainable and fulfilling careers, we must make time to care about the wellbeing of our collaborators, our users, and ourselves.” – April Wensel
Then we heard from Sarah Novotny (from Google cloud platforms) who shared how Google contributes to Open Source by supporting foundations, contributing to open source code, defining standards and a lot more. Google supports Open Source to build a stronger ecosystem together and it requires a community.
Next up was Chris Bailey (from IBM) who showed us how IBM has been committed to making Node.js enterprise ready through key contributions to the community and introduced us to Loopback, a Node.js framework for building large-scale APIs.
And of course we can't forget about Rob Tiffany (from EnterpriseIoT) who familiarized us with basic concepts and components of IoT and how they work. He also highlighted the problems that we’re currently having with IoT (complexity, lack of skill-set, integration, poor data quality, etc.) and how to simplify things by using things that work well and what we already know.
After Rob’s presentation, we had to make hard decisions – which presentations to attend next? Several were running simultaneously, so we ended up learning about the backend and frontend best practices, IoT, DevOps, Frameworks, Node.js project, Open Source, Scaling, Machine Learning, Agile processes, etc.
You can take a look at the full schedule here including the presentations.
On the last day:
This is when the workshops and Node.js collaborators summit took place. At a workshop (Code & Learn), we were able to contribute to Node.js's codebase with the help from members of the Node.js core team. We had a room filled with about 300 people working on Node.js improvements. It was a pretty fun experience for me to work in such an environment and to collaborate with the team while adding my first contribution to Node.js' project that later became part of the v11.0.0 release.
I learned some new things for myself like Machine Powered Refactoring and Web Assembly, etc. And on a nontechnical note, I discovered more about Effective Agile Processes and it’s all about people and how vital it is to make your workflow a tool that would serve your team; and if it doesn’t work, then change the process, not the people.
Overall, it was a great experience for me as a developer. I can’t wait to try a few things myself. The tech world is constantly evolving, coming up with new things and technologies, it’s important to be on top of it all.
Edited by Alysa Yamada.
You might also like...
How We Hire Engineers
The recruitment process at STRV is designed to identify the best, and to create value for every candidate. How? Our senior developers offer detailed feedback that has helped many candidates improve their skills. If you are considering apply...
STRV Academy – An Inside Look
Looking to master the latest frameworks, like React, Node.js or Swift? In just a few weeks, STRV Academy’s practical courses teach what would otherwise take months of self-study to learn.You will receive tailor-made lessons, code reviews, h...
MVI — another member of the MV* band
Every Android developer has heard about MVP and MVVM presentation patterns. Therefore, without even trying, we can easily explain the meaning of the “V,” “P” and “VM” in these acronyms. “V,” as in View, represents everything visible on the ...