How do you keep a codebase simple when you need have things in it like implementations of state of the art algorithms to compare against and the previous iterations of your own method so that you can test whether you're actually improving? Then, depending on what you're doing, there's also all the extra nontrivial code for tests and sanity checks of all these implementations.
Simplicity is a nice dream. The realities of research are very often stacked against it.
Simplicity is a nice dream. The realities of research are very often stacked against it.