3 ms·
If your .Net codebase is crufty, get some unit-tests in place and start refactoring to make it better. It could be a lot worse - you could be maintaining a lega
by squidsoup 16y ago
If your .Net codebase is crufty, get some unit-tests in place and start refactoring to make it better. It could be a lot worse - you could be maintaining a legacy spaghetti classic asp system. At least with .Net you'll have the ability to make some incremental improvements. Personally I find this kind of re-working of poorly written software enjoyable, but I may be in the minority.
- spread_thin 16y agoI wish that were an option. The mentality here is, "If it ain't (too) broke, don't fix it." Which means people actually get in trouble for doing refactor work that doesn't add new functionality. But you're right--compared to what I could be doing, this isn't a bad gig. I just wish I could be satisfied with "not a bad gig"...