Lines Matching +full:look +full:- +full:up

6 This is a short document describing the preferred (or made up, depending
8 mirror the :ref:`process/coding-style.rst <codingstyle>` document to some
35 ------------
37 Everybody thinks managers make decisions, and that decision-making is
55 painful ones.  Making small and non-consequential decisions is fine, and
56 makes you look like you know what you're doing, so what a kernel manager
65 **two** inconsequential decisions - the wrong one **and** the right one.
72 you cannot escape.  A cornered rat may be dangerous - a cornered manager
80 back-tracking is very easy: just tell everybody that you were an
89  - admitting you were an idiot is harder than it looks.  We all like to
92  - having somebody tell you that what you worked on for the last year
97    the first place, and your decision ended up being a big one after
101 admitting up-front that you don't have a friggin' clue, and telling
124 we just do both?" and look pitiful.  Trust me, it works.  If it's not
126 answer may end up being that both teams get so frustrated by the
127 situation that they just give up.
131 couldn't decide was that they were both wrong.  You end up coming up
133 have screwed up on.
137 ---------
145 theirs - and yours.
150 is fairly easy, and un-alienating them is hard. Thus "alienating"
152 no-no according to :ref:`decisions`.
161 even realizing it, and almost always with a white-hot conviction that
166 right), the harder it ends up being to apologize afterwards.
170  - get really good at apologies
171  - spread the "love" out so evenly that nobody really ends up feeling
183 3) People II - the Good Kind
184 ----------------------------
189 nobody ever believes that they're average or below-average), we should
196 Suck up to them, because they are the people who will make your job
202 good idea - go wild", or "That sounds good, but what about xxx?".  The
207 One thing to look out for is to realize that greatness in one area does
217 ----------------
225 person who lost their whole 36GB porn-collection because of your
229 Then make the developer who really screwed up (if you can find them) know
230 **in private** that they screwed up.  Not just so they can avoid it in the
237 glory, because you're the one who gets to say "I screwed up".  And if
243 ------------------
258 ends up going overboard and hiding the problem, and as they say, "On the
276 ----------
287 by trying to keep up with everybody else and running after them as fast