liveBook · Manning

Perseverance

As explained in The Creative Programmer

Perseverance is continued effort toward a goal despite obstacles, delay, or discouragement.

Perseverance is continued effort toward a worthwhile goal when progress is slow, confusing, or discouraging. In creative work, curiosity starts the search; perseverance carries it through the connecting, digging, reworking, and reviewing needed to finish. A promising idea without follow-through remains only a beginning. section 6.1 section 6.3

For programming, perseverance means resisting two unhelpful defaults: staying only with familiar solutions, and quitting the moment a difficult concept refuses to click. It does not mean blindly repeating the same failed attempt. Pause, wander, inspect the problem from another angle, then return with fresh attention. section 6.8 section 8.3.2

A long route to an idea

Charles Darwin collected information during the Beagle voyage, then kept connecting, digging into, reworking, and reviewing notes before publishing On the Origin of Species 23 years later. The useful lesson is not to copy the timescale; it is to recognize that substantial work may require revisiting evidence long after the first spark of curiosity. section 6.3

Treat perseverance as a set of adaptable habits:

  • Keep a small diary or other record of details worth returning to; creative work can lose important observations when memory is asked to hold everything. section 8.3.2
  • When stuck, temporarily do something else rather than declaring defeat; distance may let a roadblock be processed differently before you return. section 8.3.2
  • Build a regular practice, whether that produces much work or only a few heavily revised pieces; consistency matters more than a fixed quota. section 8.3.2
  • Use criticism as material for learning, and regard effort as part of mastery rather than evidence that you lack ability. section 6.8 section 6.2.4

Perseverance has limits and needs judgment. Grit is described as passion plus persistence, but persistence alone does not erase differences in potential or settle debates about talent. Nor is persistence an instruction to keep bashing at code unchanged forever: feedback, reflection, and a deliberate change of activity can make continued effort more useful. section 6.3.1 section 8.3.2

A growth mindset supports perseverance by treating creativity as developable: embrace challenges, learn from criticism, and persist after setbacks. Curiosity supplies the question, passion can help sustain attention, and perseverance keeps a programmer with the problem long enough to discover a better route. Ask yourself: am I abandoning this problem because it is truly unproductive, or because it has become uncomfortable? section 6.2.4 section 6.3.1

How The Creative Programmer covers it

How deep it goes
Explains perseverance through research links, historical illustration, growth mindset, feedback, and daily habits rather than implementation details.
Examples
Uses Darwin’s delayed publication, creative workers’ routines, programming roadblocks, and productivity practices as illustrations.
What it assumes
Assumes no language-specific background and treats creativity as a skill that can be developed.
What you can do after
Practice/perform it by sustaining inquiry, revisiting work, accepting feedback, and returning thoughtfully after roadblocks.
How it connects
Connects perseverance with curiosity, creativity, growth mindset, grit, feedback, passion, and motivation.

Also explained in

Compare how 2 books explain perseverance →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Creative Programmer. The section links point to the parts of the book it draws on.