Thanks -- I'll post a question when the need arises, but right now I'm finishing up a couple of large pieces of code and taking part in a massive system installation. No material for questions or even a meaty meditation.
My somewhat longer term plan is to start building a list of tools and techniques for doing what I call forensic software development; reviving software that works, but has no 'owner', learning what it does, and eventually re-writing the code with up-to-date practices (perltidy, perlcritic, logging and so forth).
| [reply] |
forensic software development; reviving software that works, but has no 'owner', learning what it does, and eventually re-writing the code with up-to-date practices (perltidy, perlcritic, logging and so forth)
Wow—that sounds both extremely useful for the user and extremely difficult for the developer. Certainly I've wished for tools like that before; I hope that we'll hear more about them as they develop.
| [reply] |
