Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Ha! Ha! Ha!

    Are you sure that isn't a Larry Wall joke?

    My take on your take, ie your blog on blogging, is that writing a blog has nothing to do with reading a blog. We have the impression that there is some communication taking place, but that is a mistake.

    Come to think of it, that's the problem with all communication. There is no communication.

    Or rather, what is communicationed isn't what the communicators intended.
    • No, it’s no Wall joke. It’s Sturgeon’s Revelation [wikipedia.org].

      • Ah, that was who it was.

        I am really bad with names, but good with faces, so quotes, articles, books and particularly module names are not my strong side.

        Thanks,
    • Interesting take on my take :)

      I am quite intrigued with your view on communication. I am very much focused on communication myself and I am of the opinion that communication is no where as easy as it sounds.

      Of all the software projects I have been on, all the problems were always communication problems or resource problems and not actually real technical problems.

      Technical problems can be solved one way or the other.

      One could argue that resource problems where all due to organizational problems, which again