3 ms·
> revolves around understanding other people's codebases/ideas and building things on top of other people's software But that's a completely separate topic: "s
by kazinator 4y ago
> revolves around understanding other people's codebases/ideas and building things on top of other people's software
But that's a completely separate topic: "structure and interpretation of other people's mud balls".
Don't screw up "structure and interpretation of computer programs" just because most dev work is making changes to existing code. Teach that in a different course, if you have to.
The coding that the book is based on was never common in relation to daily grunt work: business or scientific data processing and whatnot.