Bumper-Sticker Computer Science (1985) [pdf]

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 ?

Re: Bumper-Sticker Computer Science (1985) [pdf]

#5

Post by shill » Sun, Nov 30, 2014, 7:34 PM UTC

neduma wrote: post #3

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.

Re: Bumper-Sticker Computer Science (1985) [pdf]

#6

Post by Maro » Sun, Nov 30, 2014, 7:34 PM UTC

neduma wrote: post #3

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.

Re: Bumper-Sticker Computer Science (1985) [pdf]

#7

Post by mattrepl » Sun, Nov 30, 2014, 7:42 PM UTC

agumonkey wrote: post #4

japhyr wrote: post #2

"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 ?

Instant feedback makes coding more tangible but can be harmful. One may get caught in an edit-eval cycle and spend time solving the wrong problem.

Regularly stepping back and reevaluating assumptions/goals helps. (And write supporting tests, if you swing that way.)

Re: Bumper-Sticker Computer Science (1985) [pdf]

#8

Post by japhyr » Sun, Nov 30, 2014, 7:43 PM UTC

agumonkey wrote: post #4

japhyr wrote: post #2

"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 ?

For me this advice is about developing your spec to an appropriate level of detail before writing any significant amount of code. I'm still in the phase where writing code is fun, and it takes a little discipline to think my spec through enough to make my code-writing time efficient.

Re: Bumper-Sticker Computer Science (1985) [pdf]

#9

Post by buro9 » Sun, Nov 30, 2014, 7:51 PM UTC

Maro wrote: post #6

neduma wrote: post #3

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.

If you're a consultant there is still a degree of paperwork to do. Documenting the approach, the work itself, the handover, the install and troubleshooting.

If you're in big business or government then there is still paperwork. These are political organisations and even doing a good job isn't satisfactory, in many cases I'd argue that appearing to do a good job on paper is what your task really is and any delivery of a working piece of code is second to it.

Re: Bumper-Sticker Computer Science (1985) [pdf]

#10

Post by fizbin » Sun, Nov 30, 2014, 8:53 PM UTC

shill wrote: post #5

neduma wrote: post #3

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.

Heh. That's my dad's quote - I remember seeing that page tacked to his office cubicle wall back in the 90s when Unisys still employed programmers who had office cubicles.