Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Is too much abstraction a bad thing?

by Adam (Vicar)
on Jul 27, 2005 at 15:52 UTC ( #478660=note: print w/replies, xml ) Need Help??

in reply to Is too much abstraction a bad thing?

Abstraction is the essence.

In the begining there was the electron, and it was good.
Then came the electronic adder, and it was better.
Then came the machine - the computer controlled by machine code, and it was complicated.
But the engineers invented programming languages to abstract away details like memory registers and complex math, and it was Perl.

Abstractions make it easier to handle the complex. This is true in all things, not just programming. Consider the modern car. We get in and drive. We don't need to know how combustion or how a universal gear works, only that when we put our foot on the gas, the car goes. We've abstracted away the details of the car and made it easier for people to use. The same is true for code.

  • Comment on Re: Is too much abstraction a bad thing?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://478660]
[stevieb]: I don't know what you mean. I write the code in C/C++ that accesses the ICs per the datasheet, wrap it for Perl, then use them. My code ensures that the functions/methods from Perl do the right thing for the chips/sensors etc
[stevieb]: At least that's what I'm working on right now. I've also been updating my automated test software Test::BrewBuild so it handles this work properly. It's not really easy meshing high level languages with low-level hardware :)
[stevieb]: this link is probably better for an overview of my test software

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (5)
As of 2017-06-25 23:10 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (572 votes). Check out past polls.