Re:How the Pentagon's payroll quagmire traps America's soldiers
by groby_b on Wednesday August 07, 2013 @03:23AM
(#6171337)
In a reasonable world, yes. In a world where IT is a cost center, this is what happens:
1) People work around it as much as possible.
2) When the pain is unbearable, you bring in a high-priced consultant, because your engineers say something about "recompile" and "refactor". Which you as VP don't understand, are scared of, and are not willing to spend the money on.
3) The consultant puts in a week or so to hack things together. It's much cheaper than the recompile/refactor thing, and so you as VP are a hero to your bosses.
4) Since the consultant is paid hourly, documentation seems kind of pricey. Let's skip that.
5) Lather. Rinse. Repeat.
I wish this was just Dilbert, but in quite a few companies, that's reality.
Re:How the Pentagon's payroll quagmire traps America's soldiers
by sliverstorm on Saturday August 03, 2013 @03:14AM
(#6151407)
Who knows how big the program is? Perhaps it can reach a size where refactoring is just way more expensive than patching as needed.
This sounds like something with extremely high overhead, that would benefit from scale. That is to say, instead of trying to reverse-engineer and patch each module every time you need to make a change, just:
1. run the entire project through a decompiler, making sure that each generated code file on its own recompiles to something that works when linked back together with the rest of the existing modules;
2. and then use that decompiled result as the new codebase, and start refactoring.