Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: Re: Re (tilly) 2: Are debuggers good?

by davorg (Chancellor)
on Dec 28, 2000 at 21:13 UTC ( [id://48639]=note: print w/replies, xml ) Need Help??


in reply to Re: Re (tilly) 2: Are debuggers good?
in thread How to debug unknown dynamic code?

There are far too many people who (attempt to) perform programming as a income activity who aren't really programmers. If you can't program careful enough to not need a debugger, then either slow down your rate of coding, or pick a different profession. Please.

This is, of course, true. There aren't enough real programmers around to cover all the programming jobs. And as the demand for IT staff increases the problem will only get worse.

I was contemplating starting to run Perl courses in the UK, but perhaps I should just run programming courses first...

... or perhaps "programming" isn't something that can be taught.

--
<http://www.dave.org.uk>

"Perl makes the fun jobs fun
and the boring jobs bearable" - me

  • Comment on Re: Re: Re (tilly) 2: Are debuggers good?

Replies are listed 'Best First'.
Re: (davorg): Re (tilly) 2: Are debuggers good?
by coreolyn (Parson) on Dec 28, 2000 at 21:24 UTC

    Had to throw my .02 out when I read:
    perhaps "programming" isn't something that can be taught.

    IMHO its the term programming that keeps people from learning it.

    Programming is merely a stereotyped word that detracts the average person from more actively interfacing with thier computer; Therefore, programming is not a skill to be learned, but rather must be a personal goal to be attained.

    coreolyn

      Nope. I don't want someone writing a Perl module who is merely experienced at "more actively interfacing" with their computer, which to me just sounds like a "power user".

      I want a "programmer". Someone who can imagine what all the variables are doing simultaneously, and can think logical steps, and play out "what ifs". And can write robustly, knowing that people will misinterpret the interface specs. And can write good unit tests, and understand version creep and flag days and why those are bad. And why "objects" is not the cure all.

      That's a programmer, and I'm happy that the word scares off some people. Because it should. I don't want someone to "step up" from writing an Excel macro to writing control software for the plane I'm riding in. It's not a simple step. It's not even on the same scale.

      Feel free to "more actively interface" with the computer in the privacy of your own cube, but don't make me ever have to run your code or maintain it. Because, by goodness, I'd probably rather throw it away.

      Good programming is an art. Parts of it, you can get from learning. Parts of it come from experience. But parts of it seem to be just being wired the right way. And yes, most of the population is not wired the right way. I truly see that over and over again.

      -- Randal L. Schwartz, Perl hacker

        Well were definately into a matter of perspectives here. I can easily see how you can say,

        And yes, most of the population is not wired the right way

        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.

        To think otherwise simply builds cathedral's. Then again Maybe I spend too much time looking down the road rather than dealing with the present.

        coreolyn

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://48639]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (7)
As of 2024-10-09 14:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    The PerlMonks site front end has:





    Results (45 votes). Check out past polls.

    Notices?
    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.