comment on

At first when I saw the subject of this node I had an entirely different idea about what it was about before I read it. When I hear the phrase "if it ain't broke don't fix it" in my profession I get my dander up just a tad. Why?

First off lots of folks live with broken "things" such as slow computers, applications that crash all the time etc. and don't even realize that it's broke. They just just accept the status quo and reload the application or put up with delays etc.

I am a Unix Engineer by title and my job is to point out to such folks that it's broke and how to fix it. That's what I get the medium sized bucks for and when we as engineers figure out how to fix it and life gets better for the end user they are happy and I go on to the next thing that might be broke and on it goes.

Is the XP system broke? Dunno. ysth makes the statement that

Somehow, our founders have got things right.

Probably right, but how can I say? What yardstick do I have to measure "right" with in this case? What right do I have to measure it? I'm not one of the gods anyway!

Part of why I hesitate one way or another to say if the XP system is broke or not is the simple fact that I don't know what our founders had in mind and in my not-so-humble opinion they are the only ones who can say definitively if it's broke or not.

Closing thought: XP is probably the least important facet of PM to me anyway. This could be one reason I don't see the system as being broke.

Peter L. Berghold -- Unix Professional Peter at Berghold dot Net
	Dog trainer, dog agility exhibitor, brewer of fine Belgian style ales. Happiness is a warm, tired, contented dog curled up at your side and a good Belgian ale in your chalice.

In reply to Re: If (the PM XP system) ain't broke, don't fix it by blue_cowdawg
in thread If (the PM XP system) ain't broke, don't fix it by ysth

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks