Lines Matching full:you

12 good. But appreciate beauty when you see it - and let people know.
14 The code that you are afraid to touch is the code most in need of refactoring.
18 Put real thought into how you organize things.
24 the course of writing a patchset you encounter a condition that shouldn't
26 you're not sure if it can happen and not sure how to handle it yet - make it a
29 By the time you finish the patchset, you should understand better which
34 we're not stuck debugging undefined behaviour should it turn out that you were
43 Good assertions are based on state, not logic. To write good assertions, you
47 means that you can run them in only a few places in the checked in version, but
48 should you need to debug something that caused the assertion to fail, you can
61 often nudge you towards making the entire system simpler and more robust.
63 Good code is code where you can poke around and see what it's doing -
76 Pretty printers are wonderful, because they compose and you can use them
77 everywhere. Having functions to print whatever object you're working with will
87 Error messages should, whenever possible, tell you everything you need to debug
90 Tracepoints shouldn't be the first thing you reach for. They're an important
100 shockingly easy to debug once you have counters on every distinct codepath.
104 When debugging, try to get the most out of every bug you come across; don't
112 a user waiting. They'll thank you in the long run, and when they understand
113 what you're doing you'll be amazed at how patient they're happy to be. Users
119 interacting with them you can benefit from their experience.
124 This will also motivate you to make your debugging tools as good as possible,
126 time you spend at it the better you'll get, and you the developer are the
129 Be wary of how you take on and commit to big projects. Don't let development
131 wait for its proper time - but you won't know if it's the proper time for an
132 idea until you start writing code.
135 Nobody writes all perfect code that all gets shipped, and you'll be much more
136 productive in the long run if you notice this early and shift to something
138 other work you do.
150 much less risk of wasted effort if the feature you were going for doesn't work