4 ms·
Actually, no. Again, read the book. It doesn't work that way. The more competent workers will want to rewrite everything setting the whole project back. Many ti
by deelowe 13y ago
Actually, no. Again, read the book. It doesn't work that way. The more competent workers will want to rewrite everything setting the whole project back. Many times, staying with the incompetent crew is better even if it means things move slow as molasses and the final product is buggy as hell.
- meowface 13y agoI can imagine that's a very common scenario, but for a project as big as this one, and with people who are very used to working on massive projects, I would hope they wouldn't try and rewrite everything and would just try to get everything into a working and stable state.
- nknighthb 13y ago> The more competent workers will want to rewrite everything That's at odds with describing them as "competent".
- meowface 13y agoRight. In this case we're assuming the people hired are very experienced developers, who understand systems integration and large scale projects like this.
- MysticFear 13y agoNot exactly, what if the existing code/architecture has inherit security flaws in a high value Healthcare system? Something that competent workers won't just let exist to "finish" the job.
- nknighthb 13y agoI continue to believe you do not understand what a competent developer is. A competent developer will do what is necessary to accomplish the job they are given, in this case making an already-launched service work as quickly as possible. That may include unfortunate workarounds for security issues pending a real fix.