Lines Matching refs:t

14 to do with reality.  It started as a lark, but that doesn't mean that it
27   making it painfully obvious to the questioner that we don't have a clue
49 (Corollary:if the people you manage don't know the details better than
71 things that can't be undone.  Don't get ushered into a corner from which
83 you made a year ago wasn't a big decision after all, since it could be
93    wasn't worthwhile after all can be hard on the poor lowly engineers
101 admitting up-front that you don't have a friggin' clue, and telling
105 to admit that you are stupid when you haven't **yet** done the really
113 not.  After all, if **they** aren't certain whether it's a good idea, you
114 sure as hell shouldn't encourage them by promising them that what they
123 Btw, another way to avoid a decision is to plaintively just whine "can't
131 couldn't decide was that they were both wrong.  You end up coming up
156  (1) don't call people d*ckheads (at least not in public)
175 The option of being unfailingly polite really doesn't exist. Nobody will
179   frankly, "A Million Ways to Tell a Developer They're a D*ckhead" doesn't
205 smarter person hadn't thought about.  In either case, you win.
213 direction, just don't push too hard.
222 kind of realize that it wasn't **all** your fault.  Which brings us to the
226 incompetence will grudgingly admit that you at least didn't try to weasel
233 face it, it sure ain't you.
247 first you can apologize for, the second one you won't really get the
254 don't try to make it too obvious unless you really **intend** to irritate
257 Similarly, don't be too polite or subtle about things. Politeness easily
260 hammer the point in, because you can't really depend on people getting
272   a while, and you'll feel cleansed. Just don't crap too close to home.