Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

Conclusion

In this chapter, you got a whirlwind tour of the most important things you need to know about working with Docker, and containers in general. Although individual technologies may change – which container scheduler is in vogue, or how log streaming is best handled – we’ve tried to stay focused on the core theory and skills that every modern software developer should have.

We hope that you take away a few main ideas from this chapter. First, we hope you have an intuitive grasp of the problems that containerization solves for people, mainly by controlling complexity and packaging dependencies into a single artifact.

It’s also important to remember the difference between images and containers, and to get some practice building your own Dockerfiles from scratch, using the official documentation.

We hope that visiting a few more advanced topics, like how virtual machines and containers are different and how namespacing works, comes in handy...