3 ms·
To me this doesn't look a very good guideline. It's needlessly verbose and unintuitive. Instead of writing a long sprawling list of things, just using bullet po
by euske 7y ago
To me this doesn't look a very good guideline. It's needlessly verbose and unintuitive. Instead of writing a long sprawling list of things, just using bullet points and figures would be better.
It mentions the importance of getting a big picture of the code in question first, but the guideline itself is pretty bad at presenting its big picture.
Here's the gist of it as I understand:
- Long-term health of the code is important.
- Development should be incremental and steady.
- Beware of the contexts: style, use cases and technical complexity.
- Suggest them changes with reasons.
- Make it quick enough.
- rammy1234 7y agoGuidelines this big is there for a reason , lot of minds have gone behind this and every thing is a read to resonate with and come up as you understand it. Bulleted points and gist are good , but we are here to revise what we studied last night. This is a senior developer talking to a junior developer who is starting out. Also this is something go back and discuss and enhance.
- stebann 7y agoNever heard about effective patience and respect for other people's work? After all, people who wrote this have some experience...