Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: In Need of Mentoring

by mrguy123 (Hermit)
on Jan 16, 2012 at 10:00 UTC ( #948100=note: print w/replies, xml ) Need Help??

in reply to In Need of Mentoring

Perl Best Practices by Damian Conway is a fantastic way to improve your Perl programming and programming in general.
Good Luck!
Mr Guy

He who is content with his lot probably has a lot

Replies are listed 'Best First'.
Re^2: In Need of Mentoring
by chrestomanci (Priest) on Jan 16, 2012 at 15:06 UTC

    That book needs to be read with a bucket of salt.

    The problem is that it mixes things that are purely individual style, issues that are definite bugs, and everything in between, and does not distinguish between them in the text/

    For example, the author of the book favors K&R brace style. Fair enough that is his view, but not mine. I respectfully disagree. Also the author recommends me to write Some::Module::Name->new() not Some::Module::Name::new() because the latter form will cause bugs if Some::Module::Name is a subclass of another module, and does not define a constructor.

    The problem is that style issues and real bug avoidance are mixed together without much in the way of distinction and labeling. Each bit of advice comes with a few paragraphs of argument, and if you read those paragraphs you can usually (but not always) deduce which suggestions are just style and which are important, but I would hate for the book to fall into the hands of manager who does not know perl and blindly dictates that the whole book will become the company coding standard.

      I completely agree with you that blindly dictating the book as coding standard is a mistake. I think there are some great guidelines in the book but also some I disagree with.
      This book really improved my coding style and I recommend it for this discussion, but it is of course up to the user to decide which guidelines he/she wants to follow.

      I think Larry Wall sums it up pretty well:
      We do not all have to write like Faulkner, or program like Dijkstra. I will gladly tell people what my programming style is, and I will even tell them where I think their own style is unclear or makes me jump through mental hoops. But I do this as a fellow programmer, not as the Perl god...stylistic limits should be self-imposed, or at most policed by consensus among your buddies.
      I would hate for the book to fall into the hands of manager who does not know perl and blindly dictates that the whole book will become the company coding standard.
      Never had a manager who thought there was a benefit of enforcing coding styles, but I've met many coworkers who started suggesting coding styles. Most of them, they say "perhaps we should start with PBP". Those people can be easily countered: if you have converted all your OO classes to use Class::Std, come back and we'll continue the discussion". I'm still waiting for the first person to do so.

      PBP has some interesting arguments. But nowadays, I only use my copy of PBP to whack people who defend their style with "but PBP says so" over their head. My copy is quite tattered and bloody, as I'm not afraid to use it.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2021-10-25 21:18 GMT
Find Nodes?
    Voting Booth?
    My first memorable Perl project was:

    Results (90 votes). Check out past polls.