Beer.js - Debugging node.js from docker and multi source API's
One of the biggest reasons for using Docker is the isolation that it provides. Unfortunately for many developers working with Docker for the first time, this isolation also changes how they can use the tools they've typically used in the past.
With several teams, I've observed that they've moved through several stages of Docker debugging with varying levels of pain. To save you this pain we'll explore each of them with a simple Node.js app.
We'll look at how people start debugging, and move through the stages until we manage to punch a hole into an isolated container to directly debug a running process.
At the end of the talk, we'll discuss a little how you can leverage these with other technical stacks.
After seeing how much time and frustration is wasted on getting content from bad APIs and integrating with undocumented data sources – time that could have been better spent on building better user experiences - Kjell-Morten had to do something.
Now he has set out on a journey to lower the bar for frontend developers to use data and content from all kind of sources, and to move their focus from how to get the data to what they can do with it.
He will share some of his thoughts in this meetup, show a bit of what he is working on, and is eager to get feedback and hear your experiences with the topic.
Kjell-Morten started his career as a coder in the 90s, studied psychology to become an interaction designer, worked for ten years in the design+ux+tech company Netlife in Oslo, and moved to Bergen to build and lead a Netlife team there.