3 ms·
Some of the worst examples of that are when a project uses a custom build of a library of which the source no longer exists and no record of the changes exists
by koolba 10y ago
Some of the worst examples of that are when a project uses a custom build of a library of which the source no longer exists and no record of the changes exists either.
- ayuvar 10y agoReintegrating future changes in the upstream is also made nearly impossible as a result; our tech lead made a change to numpy a few years ago, didn't manage to get it accepted by the project, and we're stuck with this version until the sun burns out. If there are changes in future numpy versions we want, it's up to us to backport them, which is nowhere near our core business. There's a lot to be said for standardization and 'boring.'
- javajosh 10y agoWell you could estimate the impact of backing out of the changes on the application side, with the upside being continued savings in operational complexity. Or, you could address the operational complexity with processes or tooling - which would be easiest with something like a developer OS image.
- SideburnsOfDoom 10y agoYep, seen that. You might be thinking of tweaked builds of open-source components, but before package managers were so common, I've seen also internal projects with a `/lib` folder full of artefacts like `MiscDbUtils.dll` which are internal "useful" utility functions that are widely used. Now add in a script that updates this artefact with the latest version, breaking changes, and it all goes wrong and it's hard to find the correct previous version of the binary artefact to build your code any more. Especially if the build has been broken for a while due to the project being on the back-burner and it quietly dies when no-one is looking.
- beat 10y agoBuilds that involve non-version-controlled files that exist only on a certain developer's machine, and because that developer is a control freak (or overworked), he refuses to automate or put those files in version control...
- acveilleux 10y agoI believe this is called "Job security." I've seen it a few times including a dev deleting the source code repo and substituting all copy of a set of scripts he was responsible for with compiled binaries. This was discovered due to a platform incompatibility between one of the hosts running the script and the binary wrapping. Data was then restored from backups and dev was summarily let go.