|
|
|
|
|
by adave
1297 days ago
|
|
Imo reading gets you nowhere and is inefficient. Key piece is to add some form of self explanation or diagram to map the overall picture, since it takes a lot of repetition to understand the code flow but only hours to come up with a data flow diagram and revisit/update when needed. Even faster when someone on the team has already done it. Maybe its just me but plain text does nothing for me so i convert it into visual elements. |
|