3 ms·
Seems the most likely, the software industry is pretty bad about maintaining old tooling for this sort of thing.
by InclinedPlane 17y ago
Seems the most likely, the software industry is pretty bad about maintaining old tooling for this sort of thing.
- mahmud 17y agoSometimes tool vendors deliberately sabotage your maintenance efforts. A friend of mine called me over to show me his codebase, which is diligently maintained over 12 years using MS Visual Studio 6. As he booted the machine, a .NET update dialog popped up and he clicked "OK". .NET was updated, along with some important VS6 components, and when he fired up the IDE it told him it need to upgrade VS. After upgrading VS, reluctantly, he was no longer able to build the project.
- roofone 17y agoTo be pedantic, that's not MS deliberately sabotaging the project. That's perhaps MS being reckless with their upgrades, resulting in (I would suspect), an alienated customer. My lesson from this comment and the story is that configuration management is more important than I thought.
- phaedrus 17y agoThe code doesn't even have to be that old - in my indie game company, my partner and I often run into issues just moving code between my machine and his. Things like compiler versions, C++ library versioning issues, third party libraries. I never understood before why big businesses' IT departments are so conservative about upgrading and changing systems, until one day as I was spending my whole weekend fixing problems caused by (needlessly) upgrading to the latest version of GCC I had the epiphany, "You know, this was avoidable."
- angusgr 17y agoDid you have a separate build machine, preferably that built automatically on every checkin, so there was a canonical "it's broken here, but not there" point? (Not that this avoids this problem, it's just - in my experience - it makes it easier to pinpoint and fix.)
- dalore 17y agoContinuous Integration http://en.wikipedia.org/wiki/Continuous_Integration http://en.wikipedia.org/wiki/Continuous_Integration