This post originated from an RSS feed registered with Java Buzz
by Michael Cote.
Original Post: Selling Change, or Just Doing the Right Job
Feed Title: Cote's Weblog: Coding, Austin, etc.
Feed URL: https://cote.io/feed/
Feed Description: Using Java to get to the ideal state.
That seems to wrap up an interesting way of "selling"
what would seem like difficult to sell plans for a software
project. For example, on every piece of software that's been through a
release, there's always the desire (often
href="http://www.joelonsoftware.com/articles/fog0000000069.html">overly-zealous)
to
href="http://c2.com/cgi/wiki?RewriteCodeFromScratch">rewrite. When
you know that you should rewrite something -- because your system has
calcified, and it's no longer cost-effective to maintain and add new
features to -- you, the programmer, have to sell this non-customer
facing feature to management. It's a hard feat to go to someone who
perceives the system as working fine and convince them that "we need
to rewrite major parts of the system because they don't 'work.'"
Perhaps, as the above quote suggests, the difficulty is that
demanding a rewrite is the wrong approach. It's a bit of
spin-miestery, but the simple solution might just be "we need to
update the code to meet the new features and enable the required
functionality." That is, don't say "rewrite," just treat it like
it's the given next step in the evolution/development of the project.
Previous Topic
