A Rundown of the Perl Tips To Watch For
As I state in the permanent introduction at the top of this page, this blog is hard to write. The entries take much longer to write than most of my other blogs. The approach I have to take is:
So as you can see, I've got a fair bit of work to do. As well, blogs display entries in reverse-chronological order. It's not always easy for a reader to read a long series of related posts backwards. So I also have to decide how to present the content for three levels of reader:
Many of the entries that I plan to post here will be intimately tied to several of my other blogs. This modular approach allows "mildly interested" and "somewhat interested" readers to skip what they don't care about. But this punishes "very interested" readers by making them jump around the blogosphere for the related posts. (Yeah, but you're all big boys and girls... you can handle it. After a case study has had all it's related blog entries posted, I'll put together a PDF for it and post it on my consulting web site (with links at all the appropriate blogs). You can download the PDFs for a small donation, just to cover my bandwidth costs.)
That said, here are some of the related web-related "problems" that I hope to be solving here over the next few months:
(c) Copyright 2005-present, Raj Kumar Dash, http://perl-tips.blogspot.com/
- Come up with a web-related programming problem to be solved
- Affirm that I know how to solve the problem in Perl
- Sketch out a solution
- Write, test and modify the Perl code
- Write the blog entry
- Write a directly related entry in my MySQL-Tips blog, if necessary
- If I have time, convert the Perl code into PHP and rewrite the entry for my PHP-Tips blog.
So as you can see, I've got a fair bit of work to do. As well, blogs display entries in reverse-chronological order. It's not always easy for a reader to read a long series of related posts backwards. So I also have to decide how to present the content for three levels of reader:
- Mildly interested in at least the concepts.
- Somewhat interested in the methodology and a peek at the database.
- Very interested in all of the back-end stuff, including the programming.
Many of the entries that I plan to post here will be intimately tied to several of my other blogs. This modular approach allows "mildly interested" and "somewhat interested" readers to skip what they don't care about. But this punishes "very interested" readers by making them jump around the blogosphere for the related posts. (Yeah, but you're all big boys and girls... you can handle it. After a case study has had all it's related blog entries posted, I'll put together a PDF for it and post it on my consulting web site (with links at all the appropriate blogs). You can download the PDFs for a small donation, just to cover my bandwidth costs.)
That said, here are some of the related web-related "problems" that I hope to be solving here over the next few months:
- Customizing Perl (and PHP) scripts for parsing web server log files.
- Web server log database (at MySql-Tips blog)
- Capturing visitor info for blogs that are hosted on OPSes (Other People's Servers).
- Producing detailed blog visitor histories (at NetMetrics blog)
- Geo-plotting visitors - determining where your visitors are coming from (at GeoPlotting blog).
- Producing an animation of web visits (a map of the world with icons popping up, in an animated fashion, over their home country) (at GeoPlotting blog)
(c) Copyright 2005-present, Raj Kumar Dash, http://perl-tips.blogspot.com/
| Permalink | E-mail this post 
