3 ms·
The legacy application is probably full of undocumented special cases that are necessary to get correct results, and have to be tediously reverse engineered. I
by mrduncan 17y ago
The legacy application is probably full of undocumented special cases that are necessary to get correct results, and have to be tediously reverse engineered.
I think you hit the nail on the head right there. There is always some oddball case where workers X and Y get paid double time when there is a full moon on the third Tuesday of March in a leap year.
- edw519 17y ago"There is always some oddball case where workers X and Y get paid double time when there is a full moon on the third Tuesday of March in a leap year." And that's a tough case to program?
- wallflower 17y agoI've worked in the field of enterprise software; unfortunately, programming can be the least of your tasks. It is not a programming issue. A project manager has a lot of constituents (university employees) to satisfy. Lots of fiefdoms. It's more like a Zoo Keeper - an enterprise especially one like a university can be a complex ecoystem with its own predators - you can be in all-day meetings, dealing with the virtual ecosystem of vested interests, departments, groups who all want a say in how the software works. Pissing off someone inadvertently could cripple your project. As anyone who has tried to get the registrar to do X in Y time and has been referred to Z to get P's signature and so on, universities can operate on their time schedules and march to the beat of their own drummer. And, remember, a fair number of employees at a university who have been working there for 15 years and are used to doing things their old way might be passive-aggressive or hostile to the idea of something making a process more efficient.