3 ms·
Yeah, I've also been interested in writing more about orienting yourself in novel codebases. I don't think it's explored very much. It's a pain to write about
by eatonphil 6y ago
Yeah, I've also been interested in writing more about orienting yourself in novel codebases. I don't think it's explored very much.
It's a pain to write about because you have to find some contrived error (real or not) in a contrived app. I've got a draft of a post but without the examples filled in.
Would like to read (and share) what you've got.
- monksy 6y agoIt's not explored very much because most new developers try to push for greenfield development and they're trying to split everything up even when it doesn't need it. Now we're having multiples of codebases to comb through.
- gnufx 6y agoSo true. Also with respect to documentation, which you have to put in a blog rather than contributing it to the project where it can be maintained. It's bizarre to be literally the last port of call for work you've actually done, when people would rather refer to obsolete blogs on things you addressed years ago.
- aahortwwy 6y agoAt a previous job of mine modifying large and unfamiliar codebases was a major aspect of our team's role. I always thought it would be a good way to interview candidates, but never got to try it out.