11–19 of 19 posts
It was published 1985. Wonder if anyone is not applicable now?
Maybe this: "The job's not over until the paperwork's done." I've worked a few jobs in the last 10 years (non-gov't), and I didn't experience paperwork around programming work.
The paperwork has moved into a digital format, but it's still there.
I wish the IRS followed this advice.
"The sooner you start to code, the longer the program will take." I certainly benefit from regular reminders of this.
I'm a little stumped by that, I'm all for repl oriented development, ~zero round trip time etc etc but I have to admit that when you thought the problem through in your head long before writing any, then the right code will fall through. So are instantaneous cycles good or bad ?
Three pounds of flax.
"The first step in fixing a broken program is getting it to fail repeatably" - Tom Duff / Bell Labs
Earlier quoted context omitted.
I'm a little stumped by that, I'm all for repl oriented development, ~zero round trip time etc etc but I have to admit that when you thought the problem through in your head long before writing any, then the right code will fall through. So are instantaneous cycles good or bad ?
So are instantaneous cycles good or bad ? Three pounds of flax.
To the extent that [Agile software development] is [an excuse for not thinking], it's a bad thing. - Leslie Lamport
I think these are probably valid cultural reflections, potentially ascribable in part to the (edited, time-lapse) nature of paper-publishing versus electronic.
It was published 1985. Wonder if anyone is not applicable now?
"Allocate four digits for the year part of a date: a new millennium is coming." Nobody starts projects using two digit years anymore, right? And most of the existing software that did was patched and or replaced for Y2K. Also the part about a new millennium coming is temporarily not applicable.