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.

A Specification Language for Software 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I see the same sort of future, but without the "extinction of software engineers". Engineering is a design process, and design is something that most humans can't get right anyway. (For the case in point, see "traffic engineering" (at least in the US), "almost any random kitchen appliance", or "the i-phone." Also see the past several years of interface/interaction design theory -- which have yet to establish any sort of closed formula for addressing design issues in a generic or product-agnostic way.)

    Tellingly, I don't see Perl in the categories of Hans-Eric's blog. If programming is "repetitive and error-prone", you're doing it wrong!

    Of course, my idea of the future probably defines "tell the computer" in a slightly different way than his. For "do what I mean" to work, you need concision, which involves an advanced vocabulary, context-sensitivity, and lots of other complicated concepts which will never be accessible to the mentally mundane.

    So, how long will it take this amazing future of high-level, advanced interaction to get here? That's really a question of economics. How much are we paying the whiz-bang programmers who are building this future? And, do they have access to each other's source code?
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.