Quite early on, while starting this journey, I realized perfection is not achievable as a blogger.
It has many reasons:
Tech stacks evolve
Peopl...
For further actions, you may consider blocking this person and/or reporting abuse
If you find factual errors in your articles, there are two ways to handle them once found:
I would suggest route 1 for smaller errors and route 2 for larger updates.
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?
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.
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
100% agreed, the only way to improve and learn
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:
Ultimately, comments are feedback, so it's just about shifting that left to improve the initial quality of what most people will see.
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 π
Are lives on the lin?
No lives on the line, but some people might make you feel like that.
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
Yep no success without failure
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.