- Track abstract
- We all know how to write code, but how do we make sure that our code is good? When is code good code? Do we make good code using objects, languages with garbage collectors, encapsulating state, message passing or coding according to coding standards? Or rather, is it the way we structure our code to the problem at hand? Using the right language or tool for the right job? Do we need a bit of all of these or are there more fundamental issues in play when code turns out good?
|Day||Wednesday (10th Apr.)|