Just read a great blog post on “It’s A COBOL World” called “A Customer Visit” by an old friend. “It’s a COBOL World” is about COBOL, the workhorse of business computer processing, and the team of writers on the blog are passionate about getting more out of the code.
“A Customer Visit” addressed people’s attitudes going into a project and how good attitudes improve the value of the project. As General Colin Powell said, “Perpetual optimism is a force multiplier.”
So what did I learn about better blog posts?
A better blog post will expand our knowledge either by showing something about the main subject, or more often by bringing a side issue or a part issue into sharper focus, defining the value.
That definition is best presented as a story.
How many examinations of almost-the-same subjects are worth writing about?
All of them. Different readers find different value, see “One Man’s Wingnut Is Another Man’s Guru.”
General Powell said it one way, “A Customer Visit” said it a different way. Maybe the third way will light the spark for someone, maybe it’s a cumulative effort. It doesn’t matter. Figure your readers are interested in your subject. Concentrate on making the story interesting.
And now, the next step…(comments?)
If your AI-generated code becomes faulty, who faces the most liability
exposure?
-
Who is liable: the product maker, the library coder, or the company that
chose the product? Our Part 2 analysis examines this sticky issue if a
catastrophi...
You are right on target with your thoughts here.
ReplyDelete