Lines Matching full:don

8 A little weeding here and there goes a long way; don't wait until things have
11 Things don't always have to be perfect - nitpicking often does more harm than
27 BUG_ON(). Don't leave undefined or unspecified behavior lurking in the codebase.
33 expensive - but don't turn everything into a debug mode assertion, so that
67 issue is that we don't know where the issue is because we can't see what's
71 percpu data structures among them. Don't let things stay hidden.
83 labels, and good structure - we don't want files with a list of bare integers,
104 When debugging, try to get the most out of every bug you come across; don't
116 Talk to your users. Don't isolate yourself.
121 Spend time doing support and helpdesk stuff. Don't just write code - code isn't
129 Be wary of how you take on and commit to big projects. Don't let development
140 But don't be afraid to tackle projects that require significant rework of
143 perhaps more robust. Just don't hesitate to abandon the idea if it looks like
163 reading lots of code and looking for common patterns and issues. Don't be
169 Don't neglect your tools.
175 time is being wasted because your tools are bad or too slow - don't accept it,
179 don't go overboard. A good commit message is wonderful - but if the information