Are mistakes ok?

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Love this.
I have some drafted articles and the fear of making mistakes has kept me from publishing them so far.
I guess I'll be publishing them now. After proofreading again though 😁
It's nice that you address this!
I haven't really read similar articles... This can help/encourage people to be more straightforward with others but with themselves too!
Yeah, it seems to be a bit of a taboo at times 🤷♂️ I hope people can be a bit more open about this and this will spark a discussion.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

Quite early on, while starting this journey, I realized perfection is not achievable as a blogger.
It has many reasons:
While writing an article, which is static, you can include information that some people deem a mistake.
So how should we address these "mistakes"?
I tend to address them early on. It could include a specific version of the system the article is written for.
It could include a disclaimer that there are multiple ways of doing it, and this is just one of them.
I try not to get involved for opinions while writing an article about React for instance. Someone might address it and say Vue can do the same thing better.
It might be true or false, but it's opinionated. And not what the article was about in the first place. So I thank the person for their comment and leave it there.
What about making actual mistakes?
We should not be scared to fail, and I love to believe my blog/writing is not a set-in-stone article. When people tell me I made a mistake that can happen, I investigate and address it. Often this results in writing a secondary essay explaining the mistake I made and how I solved it.
This is, for me, the most challenging part. Yes, people read my blog and might be influenced by what I write.
But then again, is it expected always to write the perfect scenario?
Again, think about the reasons mentioned above. It might not even be wrong, but it is just missing some specific context not handled in this article.
And as always, I love to challenge people to try and find the best solution, not by reading one article or using one source. But by trying it, looking further, reading some more.
This will eventually give you a better understanding of what works for your scenario.
The main reason for writing this article is to get a conversation going.
What do you think about content creators making these "mistakes"?
Are they ok, or should every piece of content be absolute?
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter