Lines Matching refs:it

11 to do with reality.  It started as a lark, but that doesn't mean that it
14 Btw, when talking about "kernel manager", it's all about the technical
21 People", and NOT read it.  Burn it, it's a great symbolic gesture. 
24 making it painfully obvious to the questioner that we don't have a clue
34 manager must be to make it.  That's very deep and obvious, but it's not
71 a kernel manager have huge fiscal responsibility _anyway_, it's usually
78 you made a year ago wasn't a big decision after all, since it could be
83  - admitting you were an idiot is harder than it looks.  We all like to
89    deleting it, you may have irrevocably lost the trust of that
98 your mind, and make people very _aware_ of that.  And it's much easier
102 Then, when it really does turn out to be stupid, people just roll their
103 eyes and say "Oops, he did it again".  
106 actually do the work also think twice about whether it's worth doing or
107 not.  After all, if _they_ aren't certain whether it's a good idea, you
118 we just do both?" and look pitiful.  Trust me, it works.  If it's not
119 clear which approach is better, they'll eventually figure it out.  The
123 That may sound like a failure, but it's usually a sign that there was
133 with it, and perhaps more importantly, that _they_ have to deal with
136 It turns out that while it's easy to undo technical mistakes, it's not
140 However, in order to prepare yourself as a kernel manager, it's best to
151 The problem with #1 is that it's very easy to do, since you can say
153 even realizing it, and almost always with a white-hot conviction that
156 And the more convinced you are that you are right (and let's face it,
158 right), the harder it ends up being to apologize afterwards. 
163    like they get unfairly targeted.  Make it inventive enough, and they
171 scan nearly as well.  But I'm sure he thought about it. 
176 While it turns out that most people are idiots, the corollary to that is
178 knowledge that we're better than the average person (let's face it,
199 specific directions, but let's face it, they might be good at what they
201 naturally gravitate back to what they are good at, so it's not like you
208 Things will go wrong, and people want somebody to blame. Tag, you're it.
211 kind of realize that it wasn't _all_ your fault.  Which brings us to the
212 best way of taking the blame: do it for another guy. You'll feel good
215 will grudgingly admit that you at least didn't try to weasel out of it.
218 _in_private_ that he screwed up.  Not just so he can avoid it in the
220 importantly, he's also likely the person who can fix it.  Because, let's
221 face it, it sure ain't you. 
239 somebody else puts on airs, it _really_ rubs us the wrong way.  You may
241 don't try to make it too obvious unless you really _intend_ to irritate
252 without making it painful to the recipient, who just thinks you're being
265 peoples mistakes, and make it painfully obvious to everybody else that
266 you're incompetent, the obvious question becomes one of why do it in the
276 It's a great job if you can hack it.