DEV Community

Cover image for Are mistakes ok?

Are mistakes ok?

Chris Bongers on April 19, 2022

Quite early on, while starting this journey, I realized perfection is not achievable as a blogger. It has many reasons: Tech stacks evolve Peopl...
Collapse
 
lexlohr profile image
Alex Lohr

If you find factual errors in your articles, there are two ways to handle them once found:

  1. correct the article and add a short note what it said before and why it was corrected
  2. create a new article with updated information and add a reference in the old article.

I would suggest route 1 for smaller errors and route 2 for larger updates.

Collapse
 
dailydevtips1 profile image
Chris Bongers

Yeah, I've been using those two exactly like that.

Rewrite if the whole essence has changed over time, or it's too big to change
And change the small sub fixes.

How do you feel about content-writers making these mistakes?

Collapse
 
lexlohr profile image
Alex Lohr

We're all humans. All the difference we can make is learning from mistakes, be it our own or someone else's. Generally the latter is preferable, because you're not going to live long enough to make all of them yourself.

Collapse
 
thejavascripter profile image
SauhardoSengupta

In my opinion mistakes are the best way to learn to code.No programmer has ever written a programe without failing.And the next time you get the same error you will be able to understand and fix the problem quickly

Collapse
 
dailydevtips1 profile image
Chris Bongers

100% agreed, the only way to improve and learn

Collapse
 
auroratide profile image
Timothy Foster

I constantly feel this tension which is why I probably over-research and takes me so long to get something together πŸ˜…

I think this highlights the importance of, if possible, collecting feedback from peers prior to publishing. Lots of benefits:

  1. Fresh eyes tend to catch mistakes more quickly
  2. Early exposure to different opinions, some of which you might not have realized were valid
  3. Affirmation that what you've written is solid, reducing any post-publish anxiety

Ultimately, comments are feedback, so it's just about shifting that left to improve the initial quality of what most people will see.

Collapse
 
dailydevtips1 profile image
Chris Bongers

Yeah 100% Timothy.

I tried to work as your first point, but I was asking people for feedback, where person A would say write A and person B would say no write B.
(More in terms of how to word things)

That's when I decided to just publish and alter mistakes on the go.
Thanks for your feedback, appreciate your view on this πŸ’–

Collapse
 
adam_cyclones profile image
Adam Crockett πŸŒ€

Are lives on the lin?

Collapse
 
dailydevtips1 profile image
Chris Bongers

No lives on the line, but some people might make you feel like that.

Collapse
 
emil profile image
Emil

I failed so many times. I cannot count that. But still this is life and the nature of all things. Without the environment of failure there won’t be space to success

Collapse
 
dailydevtips1 profile image
Chris Bongers

Yep no success without failure

Collapse
 
booleanhunter profile image
Ashwin Hariharan • Edited

In my view, it would depend on the kind of mistake. If we're talking about mistakes in general, no writer is immune to it. In my many years of writing, I have made few minor mistakes too (mostly some API or code snippets not working the way it's supposed to). When readers encounter them, they bring it to my attention in the comments section, or over email. My response is to always thank them and make edits to the article.

If the mistakes are trivial, then it's okay. But if there's a major mistake or flaw w.r.t the very fundamentals of how something works, or logical errors/fallacies, or strawmanning, then my feeling is that the author should have spent more time in research before embarking to write the article, and also should consider proof-reading to ensure that they do not happen again.

I've seen more of this happening in web3 / blockchain puff-pieces lately - for instance claims such as cryptocurrencies are great investments because blockchains are unhackable - and this tells me that the author is coming to conclusions without doing their due diligence and research. I personally find it hard to be okay with such mistakes.

If it's an opinionated piece, it also helps to put some disclaimer along the lines of - "the ecosystem/circumstances might change in few years" if that isn't immediately obvious to the readers.