4 ms·
Don’t agree. Historic context is important to understand legacy codebases, code examples in other resources and colleague’s behaviors.
by atsjie 5y ago
Don’t agree. Historic context is important to understand legacy codebases, code examples in other resources and colleague’s behaviors.
- johnsonap 5y agoYup I think this is the most important piece of why new students should know about this, if they ever touch a legacy codebase.
- mixmastamyk 5y agoVery few legacy codebases from the tabled 90s still using tables. Yes, a few exist but not that hard to grok.
- goto11 5y agoSure, but that is an advanced subject. Don't put it before explaining what the technology actually does!
- z3ncyberpunk 5y agoyou often need to know how things came about to explain what they do and why they do it. you can't just decouple the two, and to do so at all would be dismissive of all of the work that went into getting the tool made you so shallowly want to use.