RE: How To Listen To Steem Blockchain Events Using Meeseker In Node.js
Thank you for your contribution @beggars.
After reviewing your tutorial we suggest the following points listed below:
Avoid installation steps which are already well documented.
Code sections are better displayed using the code markup, instead of placing them as screenshots. Placing the code screenshot and then the code below the screenshot is unnecessary as it's repeating information.
The structure of your tutorial is fine and also well explained. Good work!
Why is the repository and proof of work the same link?
Thank you for your work in developing this tutorial.
Looking forward to your upcoming tutorials.
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? Chat with us on Discord.
Thanks for the thorough review, @portugalcoin
I am just a very verbose person, but this is good to know for future submissions, as it will mean less typing for me anyway, ha. I generally like being as descriptive as possible and from my own experiences learning from tutorials, it's a personal preference for me that the tutorial includes everything so I don't have to context switch. But, definitely, the kind of feedback I'll take on board.
Are you referring to step 6? The code snippet from Visual Studio Code and then the code beneath? That was actually a mistake, I was in screenshot mode from the other steps and didn't realise. My apologies. Was this the only screenshot you were referring to?
If this was also in reference to the screenshots of the terminal window, those were provided for comparative purposes so that the tutorial follower would be able to reference the output of the commands with what I saw.
I removed the unnecessary code screenshot and just left the code example.
I noticed in the review under, "How would you describe the formatting, language and overall presentation of the post?" that it said average. What advice do you have to get that score up for future tutorials? Because I made sure that I made each step visually clear using proper headings, spacing out sections using horizontal lines, Markdown code blocks for code (both code and shell commands).
I think maybe this might be a good improvement to make in the official tutorial template provided by Utopian because I interpret a repository with the code in it as proof of the work done. For future reference, what is the distinction between the two of these? Should only one of them be provided in this instance?
Thanks for the thorough review, I greatly appreciate it.
Hi @beggars,
The repository would be ideal to put for example the github link of Nodejs and the proof of work the link of your code as proof that is your code.
For more information see this link
I hope to see more of your tutorials and thank you for your interest in knowing what points to improve.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Legendary. Thanks for the response, @portugalcoin love your work.
Posted using Partiko Android
You are a class act!
Thank you for your review, @portugalcoin! Keep up the good work!