Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities [email protected]
Docker, .NET Core, and the combination thereof.
The most aggravating aspect of dealing with vendors at work is that they only seem to develop for WIndows. I'll spare you my laundry list of gripes with two specific vendors, but suffice it to say, those gripes would not exist if they utilized Docker (they already use .NET Core) and didn't target Windows specifically. Not to mention, my life would be infinitely easier and our Windows licensing budget much cheaper.
I'm dealing with environment differences myself. "It works in development. It was peer reviewed. Code review passed. My changes are available in Git. It doesn't work in QA for no reason" is my current project. I'll look up a docker cert.
If you are looking to pad your resume, after learning Docker, spend a tiny bit more time to learn the basics of Kubernetes (just the basics). Maybe install Minikube. Then you can add that to your resume as well.
I've done that. But I'm reluctant to add Kubernetes into my resume, like that as I have no clue what or how to use charts.
This may be what you are trying to say but Docker makes reproducibility between environments far easier.
If it works in Docker on your machine, it will likely work in Docker equally well elsewhere. Or perhaps more important for you, if it worked for the dev, it will probably work for you too. Except for the network, the app always runs in the same environment (no matter where you deploy it).
Docker is kind of like shipping the software already installed on a laptop (just without the hardware). By that I mean that it is the software, already installed and configured, including all the libraries and utilities that it depends on.
