Code Writing - The Hemingway Method

[Uncle Gizmo]

Code Writing - The Hemingway Method!​

I was listening to Jordan Peterson talking to his daughter Mikhaila in a recent podcast. - 68. Russell Brand and Jordan Peterson

Jordan was talking about how he does his writing and how he gets started every day.

One tip he said he liked very much and he got from Hemingway!
“ stop when you are going good and when you know what will happen next”

You can listen to it yourself HERE, Mikhaila's podcast:- 68. Russell Brand and Jordan Peterson

I found it on line HERE:-
https://www.openculture.com/2013/02/seven_tips_from_ernest_hemingway_on_how_to_write_fiction.html

Extract:-
Ernest Hemingway Said:-
The best way is always to stop when you are going good and when you know what will happen next. If you do that every day when you are writing a novel you will never be stuck. That is the most valuable thing I can tell you so try to remember it.

How does that apply to writing VBA?
I was writing some complicated code, late at night, around 2 or 3am. I find late night writing advantageous because I do not get disturbed! But the problem is, you eventually have to go to bed, and then the next day you start again and you can't remember your thread. For a while now I make a point of making a note either in the code, or in a separate document where I've got to, and what I was thinking of doing next. I couldn't help thinking that’s exactly the same advice Hemingway gave for writing stories, it applies just as equally to writing code! So next time you are writing a piece of complicated code use the Hemingway Method!

 

[Isaac]

Thanks for sharing that tidbit, UG. I confess my natural tendency is to do the opposite. Stop when I'm frustrated and quite uncertain what might happen next! I'll have to try it next time ...

 

[NauticalGent]

I confess my natural tendency is to do the opposite

The struggle is real...

 

[Isaac]

Aye

 

[The_Doc_Man]

Actually, I have long espoused the same kind of rule myself.

My "Old Programmer's Rule #1" for Access is "If you can't do it on paper, you can't do it in Access." The implication is that you haven't got enough of an understanding of what you are trying to do that you could draw it out on paper, you aren't ready to implement anything. And the corollary is that when you CAN do it on paper, you know enough to resume your writing.

 

[Isaac]

Actually, I have long espoused the same kind of rule myself.

My "Old Programmer's Rule #1" for Access is "If you can't do it on paper, you can't do it in Access." The implication is that you haven't got enough of an understanding of what you are trying to do, you aren't ready to implement anything. And the corollary is that when you CAN do it on paper, you know enough to resume your writing.

I also used to tell my business partners, re: requirements gathering phase, "If you can define it, we can design it".

It never failed.

 

[Galaxiom]

This brings to mind the story of Coleridge's poem Kubla Kahn. Having dreamt of the story he began writing lucidly from the images in his head but was interrupted and when he returned to the work it was gone from his mind.

 

[Isaac]

This brings to mind the story of Coleridge's poem Kubla Kahn. Having dreamt of the story he began writing lucidly from the images in his head but was interrupted and when he returned to the work it was gone from his mind.

I'm just like that too! Except it's when I go in the kitchen

 

[isladogs]

Talking of Coleridge, I live next to one section of a long distance footpath called the Coleridge Way which runs from Nether Stowey to Porlock.
I walk part of it every day with my dogs and often use that time to think through issues where I'm stuck with coding.
When it provides inspiration, I call that the Coleridge Way.

 

[gemma-the-husky]

^^^. Ah. That's the Colins Way.

 

[isladogs]

And when inspiration fails, I also blame the man from Porlock for interrupting my thought processes....

 

[The_Doc_Man]

Sometimes, trying to get code to work right gets me to the point of being ravin' mad.

Once upon a miserable night, giving my terrible code a fight,
Trying hard to get it right, cursing my totally fogged-up brain.
Coding insight was elusive, my attempts were inconclusive;
to find a path conducive. all my efforts were in vain.
Coding had become a sad and burdensome chore.
Boredom filled me to my core.

While I struggled with a loop, eyelids started to flutter and droop,
broke away to make some soup, hoping to refresh my weary head.
Neighbor's dogs had started howling, maybe a bird had set them growling,
With their noise incredibly fouling any chance to go to bed.
Yet another wasted night was turning into a miserable scene.
Back to coding? I wasn't keen.

Tried TV to get diversion, hoping for the quick incursion
of any show to give diversion to take my brain off troublesome code.
Saw senators whose gums were flapping, the dogs outside were loudly yapping,
decided I should do some crapping, wandered towards the old commode.
Hoping that this would ease my weary body to help relax.
Hoping I didn't need Ex-Lax.

Suddenly there came a glimmer, my thoughts began to swirl and simmer,
distractions slowly turned much dimmer, I suddenly found that elusive way.
As I drained my bursting bladder, realized that my big IF ladder
was why my code was so much sadder; the insight was just as bright as day.
All those options had led to intractable spaghetti code.
SELECT CASE would lighten the load.

The fog in my brain was quickly thinning. I started to feel that I was winning
My code had found a new beginning. Proper code was falling into place.
Here I needed a simple function; these Booleans worked in close conjunction.
Success was like the finest unction to keep me working at this pace.
Time was passing faster now because the code had started to flow.
I finally saw my ducks in a row.

Into my thoughts, a sudden infraction, a totally unexpected distraction
I jump up in quick reaction to answer the telephone.
Robo-callers are not at all funny; they'll call any time to get your money.
They'll call even though it isn't sunny at the moment in your time zone.
"No I don't want to change my provider, I'm happy with my cable
And your product stinks like a stable."

Back to my keyboard I fly in a flash, hoping to give this code one more bash.
But my thoughts have turned to trash because of that stupid call.
The fog in my brain is now returning, my stomach now is quickly churning.
My eyes are dry and have started burning. I'm staring blankly at the wall.
The window shows me I've worked through the night on this programming chore.
Will I do this again? Nevermore.

With apologies to Edgar Allen Poe.

 

[Pat Hartman]

I'm always impressed by people who can rhyme. Maybe you should try rapping

 

[isladogs]

Doc
I think it should be with apologies to Samuel Taylor Coleridge as, in my opinion, its more like The Rime Of The Ancient Doc Man

 

[The_Doc_Man]

@isladogs Yes, but I'm a Poe-et at heart. Besides, I was using the pattern of one of my favorite Poe poems.

@Pat Hartman - normally, my rhyming is limited to my hobbyist writing when my fantasy characters run across a prediction or an old ballad. But for some reason this morning I got an itch and scratched it.

 

[Isaac]

Great poem! Thanks for posting.