2 ms·

Projects were typically like a month long for us as well, with some spanning 2 or maybe 3 months. I don't know I believe that something like TDD should be some

by emforce 11y ago

Projects were typically like a month long for us as well, with some spanning 2 or maybe 3 months. I don't know I believe that something like TDD should be something that's taught to us from the beginning. In my mind it should essentially be a foundation skill that becomes a platform from which you can grow from. If you are teaching a sorting algorithm then just hedge it into the class that they should split it into x methods and each method should pass test y. I do agree with your comment on how University should be concentrating on the why but showing good practices along-side the why can't hurt, even if it was just, say bonus marks for using a testing framework or following a style guide etc.

dozzie 11y ago
> I believe that something like TDD should be something that's taught to us from the beginning. In my mind it should essentially be a foundation skill that becomes a platform from which you can grow from. You see, it's a common misconception. You believe tests are one of the most important things, while they are mostly for ensuring regressions don't occur (or for basic checking if a very complicated component has some chance to work). What is really important is to have good architecture so the components are composable, and operations of different abstraction levels not mixed up. Tests are far, far after those. This is why TDD should not be taught as a universal basic block: TDD induces only bunch of supplementary code (called tests), which is not even a remote proxy for good software, while good architecture is one of the few properties that are exactly what makes good software.