Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: Perl best practices fanatism

by grep (Monsignor)
on Dec 08, 2007 at 22:23 UTC ( #655889=note: print w/replies, xml ) Need Help??


in reply to Perl best practices fanatism

If any of you had the same experiences, just drop me a note sharing your thoughts.
I don't have the same experience, but I hope you don't mind me dropping a note ;)

Having a standard is an effective form of communication when you are dealing a diverse (time or space) membership working in the same problem space. It's saves time, saves effort, and improves communication.

Think traffic laws - they are a set of standards that allow you to know what the driver next to you should do. If those standards weren't there it would difficult to drive, you would have to graft on other forms of communication like hand signals, or curse words to drive safely. What makes them work (when people follow them) is they are reasonable (at least most are), there are not a lot of objections to them, and they are codified and easily obtainable.

PBP is a reasonable set of rules, the community as a whole doesn't have a lot of objections, and it's codified in a nice package, so employing it as a standard makes a lot of sense. It saves time, improves communication, and prevents drunk coding accidents.

That being said, PBP is not the be all end all nor should it be followed blindly, but as set coding standards it has a lot going for it. If PBP (or a subset of it) stops making sense in your organization then don't use it.

grep
One dead unjugged rabbit fish later...

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://655889]
help
Chatterbox?
[davido]: I am not finding closing STDIN to be an adequate means of making getlogin return undef.
[Corion]: Maybe doing a double-fork (daemonizing) can make go that information away, but maybe not
[Corion]: But I think my knowledge of unix/Linux datastructures is several decades out of date, so I don't really know what information it keeps on processes
[oiskuu]: The useful bits that relate to your process can be found under /proc/self. What information are you thinking of? Tty name?
[tye]: I just daemonized and getlogin() still knew who I had been.
[tye]: perhaps loginuid ? Not that I concede that something not being in /proc means it is not useful.

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (8)
As of 2017-06-23 19:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How many monitors do you use while coding?















    Results (554 votes). Check out past polls.