Jump to content
Objectivism Online Forum

Reblogged: Know When You Don't Know

Rate this topic


Recommended Posts

From the annals of software development comes an interesting illustration of the difference between what one knows and what one doesn't. The below are lessons a coder learned from a bug report that bizarrely (but correctly) stated that attempting to print an example file would jam the printer:

  • Just because a bug seems impossible doesn't mean it is.
  • Abstractions are everywhere, and they can be broken. As a software guy, I believed that getting the paper into the output tray was a solved problem.
The author uses the term "abstraction" in a sense peculiar to his area of expertise, meaning an omission of "details which matter in practice, but are immaterial to the problem being solved".

The programmer reasonably thought -- but did not actually know -- that a step between the printing command and the physical document was solved. He did not know this because he did not know in detail how the printer worked. It clearly behooves us to be aware of what we really do know versus what we merely assume.

-- CAV

Link to Original

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...