I thought to add this fear, which I am surprised no one has raised as yet, which is the fear of making a mistake or fear of failure. No one likes to write about a failed attempt, even though it is through failure that you learn the most.
This leads me to the next question, if you have uploaded and published your road test and then you yourself find mistakes what is the best way to correct these. Is it:
(a) simply update report and save
(b) update report but use the "update" flag (or something else) and save
(c) write comment below report to indicate changes
Great question. When I make updates I put a comment in bold at the beginning or sometimes end of the post like this:
13 June 2018: Corrected minor typos and added demonstration video
If it is a major mistake I might use strike through and comment at the place of correction. If the correction is caught by another it is nice to give credit.
Great question. When I make updates I put a comment in bold at the beginning or sometimes end of the post like this:
13 June 2018: Corrected minor typos and added demonstration video
If it is a major mistake I might use strike through and comment at the place of correction. If the correction is caught by another it is nice to give credit.
I like doing that too, because then the reader hopefully doesn't mind f there were originally errors, because they can see (even after several years sometimes) that the author is standing by their write-up, and still maintaining it when needed. I must admit it gets very hard for some extremely old posts (e.g. some software related ones like Pi/Beaglebone many years later) where my testbed has changed over the years and it is no longer easy to re-test and support the very ancient blog posts as well as desired.
Agree it is more a wish than reality on older posts. And on some of the code I wrote early on when getting started in electronics I cringe just thinking about revisiting.
Top Comments