If you have someone who builds code and is diligent and competent and has time to test thing thoroughly and then the other person finds that things are broken and has to track stuff down and fix them (possibly with help), the MOST likely vector is dependency issues.
Just because someone built code that worked -perfectly- in their environment doesn't mean it will work at all on someone else's machine. Even if they are using tools expressly designed to synchronize/isolate these kinds of dependecies (like, say, Docker, package management tools, release kits, etc), that's no guarantee that there won't be some setup outside those tools that causes everything to go to heck until it's tracked down; everything from having the "wrong" version of a package, library, scripting language, or even the entire operating system to a difference in a harmless-seeming configuration, security setting, or permission setup.
no subject
If you have someone who builds code and is diligent and competent and has time to test thing thoroughly and then the other person finds that things are broken and has to track stuff down and fix them (possibly with help), the MOST likely vector is dependency issues.
Just because someone built code that worked -perfectly- in their environment doesn't mean it will work at all on someone else's machine. Even if they are using tools expressly designed to synchronize/isolate these kinds of dependecies (like, say, Docker, package management tools, release kits, etc), that's no guarantee that there won't be some setup outside those tools that causes everything to go to heck until it's tracked down; everything from having the "wrong" version of a package, library, scripting language, or even the entire operating system to a difference in a harmless-seeming configuration, security setting, or permission setup.