5

Docker is about handing over the weight of your incompetence in managing dependencies to your customer.

Comments
  • 1
    I'd love to learn Docker, but it looks like yet another dependency that I'll have to account for down the road.

    If I have to jump through hoops to run an application that only runs under Linux in Windows, I'll just run Linux in a VM or cloud server.

    None of my dev tools work well from Windows connecting to a remote Linux dev environment, anyway, so it all seems like a big headache for nothing.

    What am I missing?
  • 1
    @cuddlyogre My heart would say now: You're not missing anything.

    But trying to be more rational (using a lot of effort for this), Docker seems to be a good idea when the application has a lot of setup scripts and messes with configuration files of dependent software. That is, great for poorly made software.

    Imagine the following: A developer delivers a software and when the user goes to test it, he says that it is not working. The developer in turn says that it works on his machine. The solution that the customer found to make him able to use the software right away was to tell him: "Then give me your machine".

    That's what Docker is... "Then give me your machine".
  • 1
    @codingfreedom I suppose I'm fortunate in that the projects I work on are all similar since I built them and relatively small in scale. And being the only dev means I don't have to share.
  • 2
    I'd say that docker hides incompetence from developers too.

    How many times have I seen people at my previous gig turn to docker because they fail to follow the simplest of instructions or procedures to do a local project setup.

    Like not knowing how to set up hosts file and a vserver with a TLS cert...

    But what is to be expected from people committing and pushing their .env files left, right and center...
  • 0
    @CoreFusionX .env files with passwords...
  • 1
    @codingfreedom When I inherited my work from the previous people, I discovered that in several places credentials had been committed and pushed to git. They were private repos, but that is irrelevant.

    I wound up having to create a brand new repo for each project it happened in and start over from there. Meaning I lose sometimes years of history.

    Knowing what I know now, I could have removed the files with by rebasing, but even still I doubt it would have been worth the work.
Add Comment