Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^2: cron script best practices

by jimbus (Friar)
on Aug 11, 2005 at 18:33 UTC ( #483070=note: print w/ replies, xml ) Need Help??


in reply to Re: cron script best practices
in thread cron script best practices

The point of my post was that I obviously need to revisit and perhaps redesign my scripts and I wanted to see if any best practices were documented for this common pattern. Thus, there was no code or logging results given.

I'd like to think I'm a reasonable, perhaps even decent debugger... maybe a decent coder with more than 15 years experience. Unfortunately, most of that was as a consultant stuck in situations where I only learned enough of anything well enough to bodge together what I needed to integrate for that customer that week or month.

Where I'm having an issue is that when I try too embace a technology, most of the materials available is about 1 + 1 = 2, when I already know that, albiet in another language, and I really want to learn calculus. So, I go about reinventing calculus... poorly. For example, perl cron scripts digesting logs and spewing reports have been around 30+ years and perl has been around for almost 20, this pattern should be well documented.

Another example is using JDBC in JSP. I can find ten billion examples of how to do a basic query, but thats not the "correct" way to do things anymore. you're supposed to put the business logic and query code in beans and the presentation layer in the JSP page. Can I find any design patterns or tutorials on this? No, not unless I what to spend 500 pages learning a product like Struts.

Anyhow, Chiano, I didn't mean to vent at you and don't think you deserved it... it just happened :). Thanks everyone for your input, you've given me a lot of ideas and I have a few of my own... I'll keep you posted.

Thanks, :)

Jimbus

PS: I should have said I'm filling up /home. I'd thought /home was an alias for /usr/home like in freebsd, but I was mistaken
Never moon a werewolf!


Comment on Re^2: cron script best practices
Re^3: cron script best practices
by chanio (Priest) on Aug 12, 2005 at 02:10 UTC
    If you are working with Java, you must be earning a lot of money (why complain?). You might be interested in some of these books (more than 500 pages) and personal seminars: Bruce Eckell Books. He is the best of his kind and is never mentioned at Sun :) .

    What I find dissapointing of Java is that there is a lot to learn. And that your are never sure that it wouldn't change in the next release. And so much Megas to download!

    Besides, you are right: perl is McGiver-like, all resourceful. You are able to record the output of every perl script at your crontab in a provisional log file to compare it later with the output that you would get after launching every script from command line. Is it the same?

    Perl allows us to return to our basical way of solving everything just by trying things out and perhaps, reinventing several wheels. But you don't have to ask for the rules any longer. You create your own rules...

    { \ ( ' v ' ) / }
    ( \ _ / ) _ _ _ _ ` ( ) ' _ _ _ _
    ( = ( ^ Y ^ ) = ( _ _ ^ ^ ^ ^
    _ _ _ _ \ _ ( m _ _ _ m ) _ _ _ _ _ _ _ _ _ ) c h i a n o , a l b e r t o
    Wherever I lay my KNOPPIX disk, a new FREE LINUX nation could be established

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (14)
As of 2014-09-30 17:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (378 votes), past polls