Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

  (email not shown publicly)
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)

JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [], and here [] too, I ramble randomly in my philosophical blog [] and my other blog []. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Tuesday July 22, 2003
01:31 PM

Dialogue For One

[ #13618 ]
  • Me: Whooo. HTML::Template and CGI::Application together look pretty neat, but I can't expect the target content people to figure out how to do that. Better write a little wrapper to the database as a little CMS.
  • Self: Well, it sounds nice, but there's only a billion already written.
  • Me: Wull, yeah, but so what? There's a million frequency analyzers, and a million CGI toys, and a million slack bastards like me.
  • Self: You're polluting codespace.
  • Me: I'm not going to make anybody use it except me and the target, and the target has the choice of telling me to go to hell.
  • Self: Don't do it.
  • Me: Why not?
  • Self: You'll have to learn Text::Template, because the app would have to be generated on the fly. You can't store the coderefs.
  • Me: I was going to learn Text::Template anyway. Not good enough.
  • Self: Why make another CMS? God, there's so many. Just learn one.
  • Me: No.
  • Self: Why?
  • Me: Well, I need the experience coding, and it's not like I can come up with anything original.
  • Self: There's lots of other stuff to work on. Try again.
  • Me: might not suck. You never know.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • One of the dirty little secrets of software that nobody talks about is that very few programmers can actually read code. If you want to be a better programmer, cultivating that ability will serve you well.

    • It's a very good suggestion, and I think I will try to do just that. My problem with looking at other people's code has always been that my attempted adherence to style as Outlined By Larry makes my eyes averse to trying to read anything that's not indented, that's improperly indented, that does this or that, etc. As in, most code.

      Now, I'm told that PerlTidy would go a long way towards fixing something like this. But, besides PerlTidy, are there any tools/techniques you'd recommend for that sort of thi


      You are what you think.
      • It's not cheating, so if it makes your life easier, do it. It's also worth learning how to read past bad indentation and style, though it takes up so much of my brainpower I can't do it near the end of the day. Start with perltidy, find a style you like, then apply it to the code. After that, don't touch the code. Just read it.

        If you're not sure what something does, write a small program that does only that thing and see what it does. Try changing bits and pieces. It's very experimental and it worke