Cory Foy wrote:
>I know a lot of what you are going through with Legacy code
>and being told to just make hacks to make it work.
Thanks. Somehow, it's nice to know others are facing some of the same
things I am.
Today, I've been wrestling with a function that seems to be corrupting
my data. It's 208 lines long, including comments and whitespace, several
unused variable declarations, and a large comment block that has nothing
to do with the code. It also contains 2 giant while(!done) loops, takes
8 parameters, nests 5 levels deep, and uses the variable imgact and
tagend instead of idxBuf and idxEHeader. My analysis has indicated
that, yes, it harbors several bugs. But none of those bugs explain the
data corruption I'm seeing. Ugh.
BTW, I am now firmly convinced that while(!done) is a code smell. :-)
Steven J. wrote:
>It really is amazing how quickly you can switch from listening to
>defensive strikes
This is the sort of thing I was talking about training myself out
of, when I described learning to recognize "hot button" moments
I agree that's a great practice to get into. I'm still learning what my
hot buttons are and learning to manage these situations. Some things
definitely set me off. When in such a situation, it's best not to react.
That is, don't lash out, and don't give in. Rather, take a step back and
look at the big picture. You can also take steps to disarm the argument,
such as echoing back the other person's viewpoint, so he knows you heard
him, and agreeing as much as possible with him.
I've known three different people and all three
had a similar knack for needling you into a kneejerk response. All
three used different tactics to do this, but they tended to use it to
get you defending a case you had never consciously set out to make.
Another technique I've found useful: to think ahead of time about what
few things I want to accomplish in each encounter, and what things I
want not to happen. If I can, I take just ten seconds or so before a
meeting and think about these. That keeps me focused on the goal.
I think it can be very effective to own your mistakes in an
honest way
This is another excellent point. I think it lends an aire of credibility
if you can admit when you're wrong. I also think it's challenging.
>I sincerely hope things improve where you are, and I hope that the
>improvements you are making take well.
I think he's taken the first steps to cultivating trust and, in
the long run, the kind of professional atmosphere and attitude that I
find healthy.
I've definitely seen some indications of trust and respect from my peers
and from management. And I think I'm in a position where I can make a
difference. Behaving professionally seems to have generated this
opportunity. I also admit I'm both excited and nervous about it.
I should also make it clear that my manager, actually a team lead, is a
great guy and a good software engineer. He's already made great strides
establishing a work atmosphere conducive to good software, and he
supports the team well. Any difficulties are mine: I'm still learning
his communication patterns, how to hear him correctly. And anything I
wrote in my journal reflects merely my own reaction in one narrow
situation, not a verdict on my employer or any of my coworkers.
-TimK
To Post a message, send it to: extremeprogramming (AT) eGroups (DOT) com
To Unsubscribe, send a blank message to: extremeprogramming-unsubscribe (AT) eGroups (DOT) com
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*To visit your group on the web, go to:
<*To unsubscribe from this group, send an email to:
extremeprogramming-unsubscribe (AT) yahoogroups (DOT) com
<*Your use of Yahoo! Groups is subject to: