// permitted, but future edits private Color color; // may leave it unaligned Tip: Alignment can aid readability, but it creates problems for future mainte- nance. Consider a future change that needs

when a direct variable access is reasonable. This also allows accessor methods to be added in the future without breaking the interface. Cons: Properties are specified after the getter and setter methods print line Legacy AppEngine code using Python 2.5 may enable the “with” statement using “from __future__ import with_statement”. TODO Comments link￿ Use TODO comments for code that is temporary, a string repetition. # TODO(Zeke) Change this to use relations. If your TODO is of the form “At a future date do something” make sure that you either include a very specific date (“Fix by November 2009”)

synthetic/real, not all aspects evaluated, too small datasets  Conclusions  Disagree w/ every claim; future work can be dismissed Scientific Reading Adversarial Paper Summary This paper attempts to address end-to-end  Related Work  areas of related work, differences  Conclusions  summary, conclusions, and future work  References  Recommendations  Avoid sections with only one subsection (e.g., 2 and 2.1)

work calls virtual functions, these calls will not get dispatched to the subclass implementations. Future modification to your class can qui- etly introduce this problem even if your class is not currently actively considering adding other Boost features to the list, so this list may be expanded in the future. The following libraries are permitted, but their use is discouraged because they’ve been superseded relations. // TODO(bug 12345): remove the "Last visitors" feature If your TODO is of the form “At a future date do something” make sure that you either include a very specific date (“Fix by November 2005”)