Unrelated, your co-worker (and anyone else new to the codebase) would probably benefit from Commenting Showing Intent instead of print statements. I can personally attest to the direct ROI in time and effort my team has gained from it.
...that said, if he's learning said code, it may be best for him to CSI the part of the code he's studying! (It should be subject to code review, the same as anything.)
How exactly your team would need to implement CSI, and how ambitiously, is something only y'all can determine. But I think you'll find it will eliminate most cases of "I can't understand the code base".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Unrelated, your co-worker (and anyone else new to the codebase) would probably benefit from Commenting Showing Intent instead of print statements. I can personally attest to the direct ROI in time and effort my team has gained from it.
To Comment Or Not To Comment?
Jason C. McDonald ・ Jan 20 ・ 12 min read
...that said, if he's learning said code, it may be best for him to CSI the part of the code he's studying! (It should be subject to code review, the same as anything.)
How exactly your team would need to implement CSI, and how ambitiously, is something only y'all can determine. But I think you'll find it will eliminate most cases of "I can't understand the code base".