Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Every mature project I have ever joined, ever, is such a mess that it needs a map. Typically when I start a new job, I have to make that map myself, because even the senior engineers can't explain it without stammering or omitting the half of the code they don't understand anymore. Would that I'd had something just like this map every time I started a new job!


How do you go about making such a map for a large code repository? I'd really appreciate a link for reading on this subject.


I basically start anywhere and study the call graph, taking notes as I go.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: