Re^5: perl & SQL best practices

Tell me what you do or would do as a programmer if you had complete control over your db server.

How many times do I need to repeat: IT DEPENDS. Define goals. Measure. Know what the budget is. Work out what needs to be done. There are no magic bullets.

Of course, we all use strict.

That's like saying: "what should I do when I need to transport something? Of course we all check our headlights first." If you don't tell me what you need to transport from which pickup point to which destination, at what time, what the budget for it is, what your resources are and when it has to be there, don't expect me to tell you whether you should use a bicycle, a pick-up truck a train, or whether you should hire a specialist company. Magic bullets do not exist.

Do you have similar rules you follow

I do have rules I follow (but they aren't as mindless, boring and and a bit more useful than "use strict"), and they are: do not do anything without knowing what's going on, what the goal is, and what the budget is (budget is to be taken in a broad sense. It includes, but is not limited to: money, people, time frame, regulations, knowledge). Aka, don't run around as a headless chicken, going in any direction monks in the peanut gallery are shouting to you.

Comment on Re^5: perl & SQL best practices

Replies are listed 'Best First'.
Re^6: perl & SQL best practices by doom (Deacon) on Apr 30, 2012 at 19:05 UTC
... as mindless, boring and and a bit more useful than "use strict" .. Not to be picky or anything, but the advice to "use strict" is not mindless, nor is it not useful, so you've got two obvious strikes out of three (and an umpire call on the third). The point the OP was making should be obvious: there are indeed areas where a consensus exists on what's the best practice, and he wants to hear about others. I do have rules I follow ... and they are: do not do anything without knowing what's going on So you mean you never do anything?	[reply]
Re^7: perl & SQL best practices by JavaFan (Canon) on Apr 30, 2012 at 19:35 UTC
Not to be picky or anything, but the advice to "use strict" is not mindless, nor is it not useful, so you've got two obvious strikes out of three (and an umpire call on the third). In the grand scheme of things, "using strict" is mindless, boring, and compared to other things, utterly unimportant. It's on the list of "useful things to do", around place 3000, along with eating enough fruit and vegetables. "use strict" isn't the magic bullet some people think it is. Slapping "use strict" on a program doesn't make it better. The point the OP was making should be obvious: there are indeed areas where a consensus exists on what's the best practice, and he wants to hear about others. Whether or not there's consensus, the point is, the OP remained too vague on his circumstances to even determine what area he's talking about. So you mean you never do anything? No, it means I'm informed.	[reply]
Re^8: perl & SQL best practices by girarde (Hermit) on May 01, 2012 at 01:47 UTC
`use strict` would be the "wear pants to church" of perl, if there were a significant problem of people going to church without pants. But there is a significant problem of people who don't `use strict`.	[reply] [d/l] [select]


Welcome to the Monastery
	PerlMonks