Post Reply 
Engineering Procedure
08-03-2019, 12:56 PM
Post: #1
Engineering Procedure
Seen by many: enjoyed by a few; understood by ?
[attachment=7578]

BEST!
SlideRule
Find all posts by this user
Quote this message in a reply
08-03-2019, 06:25 PM
Post: #2
RE: Engineering Procedure
I imagine it's understood by most people on this forum.

An hour-long video about the oberon language has a couple of quotes I really liked (at around 36 minutes into in, give or take):
  • Programs must not be regarded as code for computers, but as literature for humans.
  • Reducing size and complexity is the triumph.

http://WilsonMinesCo.com (Lots of HP-41 links at the bottom of the links page, http://wilsonminesco.com/links.html )
Visit this user's website Find all posts by this user
Quote this message in a reply
08-04-2019, 05:56 AM (This post was last modified: 08-04-2019 05:57 AM by toml_12953.)
Post: #3
RE: Engineering Procedure
(08-03-2019 06:25 PM)Garth Wilson Wrote:  I imagine it's understood by most people on this forum.
  • Programs must not be regarded as code for computers, but as literature for humans.
  • Reducing size and complexity is the triumph.

Most places I worked use these criteria:
  • Programs must not be understandable by anyone else. Your job security depends on this.
  • We get paid by the number of lines of code we generate. Why use ADD YEAR-1 TO YEAR-2 GIVING YEAR-3 when you can create many sub-expressions first?

Tom L
I think therefore I am-Descartes
I think therefore you are-Gorgias
You're not here to think-Army Sergeant
Find all posts by this user
Quote this message in a reply
08-06-2019, 08:37 AM
Post: #4
RE: Engineering Procedure
(08-03-2019 06:25 PM)Garth Wilson Wrote:  I imagine it's understood by most people on this forum.

An hour-long video about the oberon language has a couple of quotes I really liked (at around 36 minutes into in, give or take):
  • Programs must not be regarded as code for computers, but as literature for humans.
  • Reducing size and complexity is the triumph.

Underneath Niklaus Wirths heading "What have I learnt?" at https://www.youtube.com/watch?v=EXY78gPMvl0&t=1975s you can find:
  • Writing a program is difficult
  • Writing a correct program is even more so
  • Writing a publishable program is exacting
  • Programs are not written. They grow!
  • Controlling growth needs much discipline
  • Reducing size and complexity is the triumph
  • Programs must not be regarded as code for computers, but as literature for humans

Great and humble insights from a real genius.

12C 15C 15C-LE 16C 17BII 19BII 27S 32SII 38C 42S DM-15CC
Find all posts by this user
Quote this message in a reply
08-07-2019, 04:52 PM
Post: #5
RE: Engineering Procedure
Thanks for sharing.

From my experience complexity (or unreadability) comes from (a) vanity or (b) incompetence. In the case (b) the one writing something complex or redundant or verbose, doesn't realize how to make it simpler.

For me a program/math model can be even long, but it is easy to read, change, update, understand.

Wikis are great, Contribute :)
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)