This contribution was a bit more technical than what we're used to seeing in the Blog category, but that's definitely not a knock on it. It certainly seems like a valuable update. However, there are some issues with it.
First, is the fact that while parts of the C# library are open source, not all of it is. And Visual Studio is essentially closed source, despite having some open-source plugins. So while your solution itself is open source, the software being used is not entirely in our categories.
Another content issue is that this post relies very heavily on existing knowledge on the part of the reader. As I wrote, being technical is not a knock, but it's good to make the content more accessible to a general reading public. Explaining what Anole is, for instance, would have been good. And also a positive for you, as the extension's developer.
While the post is generally quite well written, there are also issues of style and proofreading. I'll cite a couple of examples:
"However with an alternative binding provider these need not be relied upon" really needed a couple of commas. It would be easier to read as: "However, with an alternative binding provider, these need not be relied upon."
"While I've long been a handy user of code completion for some while" is redundant, and looks to be the result of a sentence what was partially edited. You don't need both "long been" and "for some while."
Greater focus on proofreading could have really elevated this post, to my mind.
Thank you for your contribution.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Thanks @didic for taking the time moderate and offer feedback. I agree with your remarks and have made the suggested revisions. While it's no excuse, those groaners that I didn't catch do illustrate some consequences of proofreading sleepy ;)
Again, your thoughtful response was much appreciated.
Thank you for your review, @didic!
So far this week you've reviewed 2 contributions. Keep up the good work!