> Question from a very amateur coder: why would I look at Python for performance when Go exists? Many things can be "fixed" if you choose to go to another syst

> Question from a very amateur coder: why would I look at Python for performance when Go exists? Many things can be "fixed" if you choose to go to another system. Good developer environments limit the supported tools, languages and packages. This comes from several issues: * When something goes wrong at 2 a.m., is the developer available going to be able make a reasoned decision how to fix the program? * Can you hire people with a mix of Python and Go experience? * If you want performance, why not choose a faster variant of Python so you stay in the same skill set? * You successfully built a Go program, but did you document your development? Did you set up a standard environment? What about CI/CD and automated testing? When you leave your position (and you will someday), who is really able to take over managing that software? > My coworkers who don't know Go understood the code just fine. Understanding and groking are two different things. I'm sure they looked at the code, nodded their heads that it makes sense; however, I suspect that if you asked one to modify the program with a new feature that they suddenly will see all the things that they don't know, from getting their environments working to subties in the language's mechanics. Environments are standardized to prevent having these types of issues between workers. Software development is ultimately about supporting the people and business goals in the company.