科技回声

"The sooner you start to code, the longer the program will take."I certainly benefit from regular reminders of this.

I went through each quote carefully while adding some missing ones to my fortune clone/database at <a href="https://github.com/globalcitizen/taoup" rel="nofollow">https://github.com/globalcitizen/taoup</a> and noticed two things versus modern sources: (1) The weight lent to optimization related concerns seems higher than today. (2) Comprehension of the non-electronic context of programming seems higher than today.I think these are probably valid cultural reflections, potentially ascribable in part to the (edited, time-lapse) nature of paper-publishing versus electronic.

I've always been fond of Thompson's rule for first-time telescope makers: "It is faster to make a four-inch mirror then a six-inch mirror than to make a six-inch mirror."

With regards to the Linux kernel bug in another thread today..."The first step in fixing a broken program is getting it to fail repeatably" - Tom Duff / Bell Labs

> Don't make the user provide information that the system already knows.I wish the IRS followed this advice.

If this was published now, it would be "Computer Science in a Tweet"

It was published 1985. Wonder if anyone is not applicable now?