> From ad-hoc approaches to the extremes of elaborations that attempt to solve every possible future problem. If you're writing code that needs to be maintaine

> From ad-hoc approaches to the extremes of elaborations that attempt to solve every possible future problem. If you're writing code that needs to be maintained (i.e. not just run a few times to generate results for a paper, but read and written by several different people over time) this is pretty bad and leads to much more technical debt than would otherwise be accumulated. This is the type of thing you learn to avoid by working in industry a few years and is why experienced ICs are paid more than new grads.