It's Called Work-Life Integration, Honey

The eternal developer defense mechanism: "It works on my machine." Sure, your unique configuration of 17 Chrome extensions, that one specific Node version, and the blood sacrifice you made to the compiler gods made it work. But unless you're planning to ship your entire laptop with the product, that's not exactly helpful. The seasoned developer on the right knows better—reproducible steps are the difference between solving a problem and just bragging about your magical computer.

Content Other professions hoping that their project works perfectly Programmers finding an error but it repeats every time they compile

The prison conversation we never wanted to see: a hardened criminal boasting about murder while our innocent developer admits to testing in production. And somehow, the murderer is the one horrified! Testing in production is basically the digital equivalent of performing heart surgery with a butter knife while the patient is giving a business presentation. Sure, it might work, but you're one misplaced semicolon away from bringing down an entire company and making your Slack notifications explode at 2AM. Even serial killers have standards, apparently.

Content THE TESTS YOU ADDED ARE 10X MORE COMPLICATED THAN THE CODE ingflip.com

Content How much code coverage do we have ? We don't write tests

Content 3 Building the image using docker run build . --networkhost fixed the issue for me. The error I was getting was caused by Docker not being able to access the Internet, so spoonfeeding it "hey, just use host" seems to have fixed the problem. Share Follow answered Jan 27 at 18:35 walnut salami 2,790 0 1 11 33 3 It's ... kind of surreal googling an error, opening a stackoverflow answer and finding out that both the question and the answer are mine but several months later - walnutsalami May 24 at 9:24