Style Guide - adventures-in/projects_summary GitHub Wiki

The set of guidelines below are intended to be a large, potentially conflicting set, some subset of which can be selected for a particular project.

1. AVOID dead code Relevant examples:

• Style guide for Flutter repo > Lazy programming: “Write what you need and no more, but when you write it, do it right.” (and other relevant points)
• [Style guide for Flutter repo > Avoid abandonware]: “we delete rather than commenting out code. Commented-out code will bitrot too fast to be useful, and will confuse people maintaining the code.”