Lines Matching refs:it
14 to do with reality. It started as a lark, but that doesn't mean that it
17 Btw, when talking about "kernel manager", it's all about the technical
24 People", and NOT read it. Burn it, it's a great symbolic gesture.
27 making it painfully obvious to the questioner that we don't have a clue
39 manager must be to make it. That's very deep and obvious, but it's not
76 a kernel manager have huge fiscal responsibility **anyway**, it's usually
83 you made a year ago wasn't a big decision after all, since it could be
89 - admitting you were an idiot is harder than it looks. We all like to
95 deleting it, you may have irrevocably lost the trust of that
104 your mind, and make people very **aware** of that. And it's much easier
108 Then, when it really does turn out to be stupid, people just roll their
112 actually do the work also think twice about whether it's worth doing or
113 not. After all, if **they** aren't certain whether it's a good idea, you
124 we just do both?" and look pitiful. Trust me, it works. If it's not
125 clear which approach is better, they'll eventually figure it out. The
129 That may sound like a failure, but it's usually a sign that there was
140 with it, and perhaps more importantly, that **they** have to deal with
143 It turns out that while it's easy to undo technical mistakes, it's not
147 However, in order to prepare yourself as a kernel manager, it's best to
159 The problem with #1 is that it's very easy to do, since you can say
161 even realizing it, and almost always with a white-hot conviction that
164 And the more convinced you are that you are right (and let's face it,
166 right), the harder it ends up being to apologize afterwards.
172 like they get unfairly targeted. Make it inventive enough, and they
180 scan nearly as well. But I'm sure he thought about it.
186 While it turns out that most people are idiots, the corollary to that is
188 knowledge that we're better than the average person (let's face it,
209 specific directions, but let's face it, they might be good at what they
211 naturally gravitate back to what they are good at, so it's not like you
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
222 kind of realize that it wasn't **all** your fault. Which brings us to the
223 best way of taking the blame: do it for someone else. You'll feel good
227 out of it.
230 **in private** that they screwed up. Not just so they can avoid it in the
232 importantly, they're also likely the person who can fix it. Because, let's
233 face it, it sure ain't you.
252 somebody else puts on airs, it **really** rubs us the wrong way. You may
254 don't try to make it too obvious unless you really **intend** to irritate
265 without making it painful to the recipient, who just thinks you're being
279 peoples mistakes, and make it painfully obvious to everybody else that
280 you're incompetent, the obvious question becomes one of why do it in the
290 It's a great job if you can hack it.