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 ]

Ovid (2709)

  (email not shown publicly)
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Thursday April 17, 2003
11:01 AM

Going backwards

[ #11703 ]

I have an object that uses many helper objects to send messages back and forth. For some reason, I struggled with the exact implementation of those helper objects and just couldn't get them quite right. My tests would pass, but I would get stuck on the code and didn't get an API fleshed out.

This morning, I realized that I had it backwards. I'm now writing the main object and the API of the helper objects is incredibly obvious. I don't have to stop and think about how they work, I just know. Work is going much faster now. I'm going to have to remember this in the future.

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.
  • Hi,

    This sounds interesting, could you explain it more thoroughly... I often struggle with having made bad design decisions so I am always open to smart ideas and designs or architectures
    • It's pretty simple, really. Let's say that I have an object that sends messages to other objects. We'll call those "helper objects". What API should I use with the helper objects? If I start by trying to design them, it may not be immediately clear how they are used.

      For example, I have a variant of a status system that I've been using, but I needed to improve on the old API. My purchase orders can be "pending", "sent", "cancelled", or "received". These statuses are actually helper objects that allow