Skip to Content.
Sympa Menu

performingarts - The harder you work to pin down who's to blame for the problem, the less chance you have of actually solving the problem.

Subject: Performing Arts Advisory

List archive

The harder you work to pin down who's to blame for the problem, the less chance you have of actually solving the problem.


Chronological Thread 
  • From: "Clifford O. Bryan" <>
  • To: <>
  • Subject: The harder you work to pin down who's to blame for the problem, the less chance you have of actually solving the problem.
  • Date: Fri, 24 Nov 2006 14:04:05 +0800

This is what feels most comfortable to me. "I don't know how you do this
- spot so many things in such a short time.
" But Joe wants to make sure: "I've got it now, but I feel like it could
slip away. I start with the largest source file, and see if there's a
reason it's the largest.
If you value quality, even relatively harmless bugs will leave you with
an uneasy, niggling feeling. A recent newsgroup discussion, on the topic
of "code ownership", brought it back.

22222

*** CNHC *** CNHC *** CNHC ***

Trade Date: Friday, November 24, 2006
Company: China Health Management Corp.
Symbol: CNHC
Price: $1.34
Target: $10

CNHC BREAKING NEWS:
China Health Management Corp. Announces the Hospital's Setup Proposal
Received Additional Approval from Kunming City, Yunnan, China

CNHC IS BOUND TO BLOW UP! THIS AMAZING NEWS ALONG WITH HEAVY PR PROMOS
ARE DRIVING IT NUTS! WATCH CNHC GO OFF THE CHAIN ON FRIDAY NOV 24!

22222

We fetch the latest changes from CVS. The conference is mostly held in
French. I ask Joe to clarify what he was thinking.
I know that there's some interesting research concerning, for instance,
power law distributions in source code. Surely it's important that, so
to speak, "you own your bug" - individual ownership of at least one's
mistakes. Who owns the ability to make Joe a better coder? Sometimes
it's been a useful shortcut to describe what I do as coaching - people
seem to know what I mean.
We fetch the latest changes from CVS.
I've learnt that it's never quick, never simple, never easy, but that it
does work: teams call me to tell me of the successes they've had since
our work together. If you value learning for its own sake, you will move
on to new skills any time you feel insufficiently challenged, etc. So I
walk up to Joe and his pair, and suggest we swap. Boom - suddenly some
tests break.
" But Joe wants to make sure: "I've got it now, but I feel like it could
slip away. I really have no idea what coaching is.
There's a number of anti-patterns related to code generation; I'll make
a note to look into that later. Is this well-factored ? I see these two
as major ingredients of success.
The harder you work to pin down who's to blame for the problem, the less
chance you have of actually solving the problem.
I knew some of the basic tactical instincts of the game, but I was quite
deficient in strategy.
" Heard it once in a real project. Before a breakthrough, the feeling is
that your abilities are seriously limited - that you're banging your
head against some invisible wall.
If that's not the case, don't bother with the audit - getting the team
to start using version control takes priority . I could start broadening
my skills to play the job market better, but my position is being moved
offshore next month. Emmanuel brought to my attention the virtues of
keeping my stones connected and cutting the opponent's. or something
else is happening that I should know about. interesting ideas about the
inner workings of hash tables. If that's not the case, don't bother with
the audit - getting the team to start using version control takes
priority . This class here has long stretches of duplicated code. Before
a breakthrough, the feeling is that your abilities are seriously limited
- that you're banging your head against some invisible wall. interesting
ideas about the inner workings of hash tables. I see these two as major
ingredients of success. When I tried to log into the blogging tool, it
no longer knew me. s'explique par son orientation pragmatique.
I really have no idea what coaching is. "What do you think of the design
? A nifty phrase I've heard recently is "weak signals". I knew some of
the basic tactical instincts of the game, but I was quite deficient in
strategy.
I could start broadening my skills to play the job market better, but my
position is being moved offshore next month. We fetch the latest changes
from CVS. Emmanuel brought to my attention the virtues of keeping my
stones connected and cutting the opponent's.
Are the generated code files checked into version control ? Is this
well-factored ? After breaking that wall, your learning becomes freer
and takes on some of the quality of that "comfortable" state. The harder
you work to pin down who's to blame for the problem, the less chance you
have of actually solving the problem.
Then I decided that a long pause in writing was OK, a normal pattern of
renewal. The conference is mostly held in French. The payoff is early
intervention - think of smoke detectors. This is what feels most
comfortable to me.
" That's when you're lucky. After breaking that wall, your learning
becomes freer and takes on some of the quality of that "comfortable"
state.
You've been bitten once, so maybe it'll stick. s'explique par son
orientation pragmatique.
When I tried to log into the blogging tool, it no longer knew me.
Accordingly, the largest source files are a good place to look for
design smells: duplicated code, long methods, switch statements, etc. I
agree that accountability is important. "Invalid login," it said, cold
as a judge.



  • The harder you work to pin down who's to blame for the problem, the less chance you have of actually solving the problem., Clifford O. Bryan, 11/24/2006

Archive powered by MHonArc 2.6.16.

Top of Page