comment on

However, from my humble point of view it seems to me that if indeed they aren't wired the right way there's a problem with the interface not the people.

Nope. Some people just don't get abstraction or clear sequential logic, or many of the other things necessary to write maintainable, practical code.

Ever ask someone for directions to a place you're unfamiliar with, and end up totally lost? Probably because that person couldn't give clear directions, ever. Some people just can't do that.

And some people just can't program. It's not the interface. It's the person.

There's no moral statement here. It's just an attribute. I can't draw a picture worth beans. Am I less smart because of that? No. I just stick to programming, and hire the people who can draw and can't program. {grin}

-- Randal L. Schwartz, Perl hacker

In reply to Re: Re: On being a programmer by merlyn
in thread How to debug unknown dynamic code? by gaspodethewonderdog

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.


P is for Practical
	PerlMonks