comment on

After getting older, but not necessarily wiser, I've since learned what works best for me is to tell the user to "show me what it is doing". This way, you're not admitting anything, nor are you denying anything.

A very sage piece of advice
I'm into my second decade of programming and engineering. And a few things still stand true:

the basic defect rate is still around one error per hundred lines of code.
Industrial strength testing and review will get about 99% of those, which means each year of coding I leave about one real bug. Somewhere.

Engineers are socially inept.
Conjugate buggy: my design is perfect; your design is interesting; his design is broken; their design is crap.

In reply to Re: Re: What Kind Of Programmer Are You? by thoglette
in thread What Kind Of Programmer Are You? by jcwren

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