JSJ 255 Docker for Developers with Derick Bailey
Docker for Developers
When you are learning how to cook on a daily basis, you rely on a recipe book which has the list of ingredients and instructions. You put all the ingredients together following the steps to produce the dish you are aiming to achieve. This scenario is an analogy to the software recipes book.
"The ultimate goal of any recipe should not just be to copy and paste and produce that one result. It should really be to look at what ingredients were used, which ones worked well together, and why they worked well together and ultimately create a deeper sense of understanding for what you're cooking." - Derick Bailey
In the software recipe book, the tools and commands represent the ingredients. A developer puts the ingredients together to produce the expected outcome. The ingredient list is a set of commands, and each recipe has a set of cooking instructions.
Misconception on Docker
Originally, Derick's mentality on Docker was it's an up-stool. There was a giant blog post that confused many years ago because of a conversation that started from one person who just wanted to start a small application. Buzz words and nonsense things were thrown eventually puzzled people. Derick's introduction started with that event, and it caused him not to touch Docker for a very long time. For the longest time, he assumed that Docker was only for DevOps people. He thought that Docker was of no use to him. He just used Heroku or simple DigitalOcean startups with Wordpress most of the time.
Importance of Learning Docker for JS Developers
AJ: Gitlab and Gitti Cory: Prettier and a steering wheel desk on Ebay Joe: Flexbox Zombies and Angular workshop in North Carolina Aimee: What No One Told You About Z-Index, haircut, and shooting Charles: JS Remote Conf, The Invisible Sales Machine Derrick: Debugging Docker Images, EditorConfig, Tokaido board game, YouTube gaming channel: Code-Ninja Gaming, and self-care