Lines Matching full:things

7 every day; look for little things that are out of place or in need of tidying.
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
18 Put real thought into how you organize things.
71 percpu data structures among them. Don't let things stay hidden.
91 tool, but always look for more immediate ways to make things visible. When we
98 use, and many complicated internal operations with lots of things that can
105 rush to fix the initial issue. Look for things that will make related bugs
118 Users notice all sorts of interesting things, and by just talking to them and
134 Expect to throw a lot of things away, or leave them half finished for later.
144 it's going to make a mess of things.
149 things that improve the codebase in their own right. When that happens there's
156 Instead of always tackling those big projects, look for little things that
164 afraid to throw things away and do something simpler.
166 Talk about your ideas with your fellow developers; often times the best things