This is for betterscientificsoftware/bssw-blog-planning#35.

I also added a little more text.

I still need to fill in some references and then I can do some more detailed
editing.

According to emails "count-words", this is currently 1935 words long.  (The
target is about 1500 so this could use some editing to reduce length.)

NOTE: I generated this hero image with Google Gemini Advancec using the
prompt:

  generate an cartoon image of software depicted as a set of gears and showing
  the hand of a mechanic with a wrench

This was the third of three generated images.

If there is a desire for different hero image, it should not be too hard to
generate one.

The tool wikize-refs.py is refusing the recognise the usage of the reference
[se2s-book-2016].  Perhaps this will help?

The error was confusing but I misspelled one usage

This messed up the numbering and the links.  But I can fix those manually in
the next commit.  I will not run this script on the file after this.

…fs.py

No sure what happened here but it was easy enough to fix manually.

The tool wikize-refs.py needs more unit testing and test cases.

NOTE: I also added some missing reference placeholders [???] in case I want to
add those.

These were left over from when I was using bullets for these paragraphs.

This reduced the length a little but up to the end of the Summary section this
is still 1931 words (according to emacs 'count-words').

All of the references should be complete now

I added mentions of code formatters and other tools like static analyzers and
runtime memory checkers, as suggested by @ksbeattie.

I also changed the reference from the book chapter "Testing of Scientific
Software: Impacts on Research Credibility, Development Productivity,
Maturation, and Sustainability" to shorter articles on the bssw.io site
itself.  (We should likely reference that book chapter in those other bssw.io
articles.)

I also added another reference related to testing and had to shift all of the
latter references.  (I could not use wikize-refs.py to do this because of the
off-by-one issue.)

Added some more text as suggested in review by @ksbeattie.

I also added a reference for more info on picking an open-source software
license.

Improving this text was suggested by @ksbeattie in his review.

Just need to fill in the day on Sept this gets published

I noticed a few things after letting this sit for several days, including a
few typos that Grammarly.com missed.

minor edits

minor edits