http://qs1969.pair.com?node_id=407759


in reply to Re: Appropriate amount of abstraction
in thread Appropriate amount of abstraction

Why stop with a "root connection with core Perl code"? Perl is an abstraction. SQL is an abstraction.

Because Perl and SQL are my starting-points as a programmer. I'm not interested in the details below my point of entry but neither do I wish to do most of my work in an abstraction layer which is too far removed from the core language. I know TIMTOWTDI at the end of the day but I just wonder how far the abstracting goes before you get layers built with, say, Maypole as one of the dependencies and all you have to write is:

#!/usr/bin/perl use Application; use strict; my $app = new Application; $app->build($data);

Replies are listed 'Best First'.
Re^3: Appropriate amount of abstraction
by revdiablo (Prior) on Nov 15, 2004 at 18:26 UTC
    Perl and SQL are my starting-points as a programmer. I'm not interested in the details below my point of entry but neither do I wish to do most of my work in an abstraction layer which is too far removed from the core language.

    Your meditation asks, "what is an appropriate level of abstraction?" It sounds to me like you've already decided this. For you, the highest appropriate level of abstraction is Perl and SQL. That's a fine choice to make, but it makes your question seem a bit misleading.

    I think chromatic was simply trying to make the point that choosing the level that's "abstract enough" is somewhat arbitrary. I'm sure you have reasons for choosing where to draw the line, but, at the end of the day, the most important thing is whether the application does its intended job.