A little bit of advice for everyone (on how to ask, and how to respond)

[mattaereal]

Hi there! This will be quick, just bear with me :)

For those receiving answers, know in advance that this course involves challenging yourself every-time you go further. There are some things that you need to improve in order to be able to reach your full potential as a blockchain dev! 💪🏽

We can spend all day fixing your typos, or declaration errors, but what would be the point of doing so if you have not developed your own debugging skills, taking away the possibility to learn to apply solutions for yourself?

With all due respect please:

• Practice how to read errors in general, and track down what could possibly went wrong thinking .
• Use patrick's code as a reference for each project. Make his code work factory_worker .
• Compare both projects, and try again cyclone .
• After all that, come here again, and post the problematic, explaining what you've done and where you at question .
• Additionally, please try to format your messages accordingly, there seems to be mixed messages and code along your posts smile

I've been answering things in the discussion forum, and I've seen some incredible users helping out others in a manner which I don't necessarily interpret as 'help'.

So, as an advice to those incredible souls out here (if I may), mediate for a second on the following.
What I'm giving out as an answer:

• possibly answers what the question asks? is really helpful?
• is complete or missing context? can be easily reproduced?
• has some links / tests / further explanation to back up my argument?
• hasn't been answered yet?
• will leave the user with meaningful information and the tools to learn how to fix it themselves or will I fix it for them without giving them the opportunity to think about it for a second?

Happy hacking :))

PS:
I've seen many people suggesting as a fix when yarn fails to run / install packages (because of misconfiguration), to run it with sudo.

PLEASE LET THAT BE THE LAST THING YOU DO WHILE RUNNING OTHER'S CODE ON YOUR COMPUTER.
Really, the last thing you want to do is give other's code (or unknown code) the opportunity to run with administrator privileges.

[krakxn]

In addition to the "I've seen many people suggesting as a fix when yarn fails to run / install packages (because of misconfiguration), to run it with sudo".

I've seen so many people pushing to GitHub without a .gitignore. Even though—in the course's context—it is not a big deal, carelessness—especially in small-scale projects—is precisely how bad habits arise, whether it be a incomprehensible codebase or so. For people who wish to pursue this field further, why not minimize even the slightest possibility of any kind of a fatal error in the future, and maintain a clean codebase w/ at least the basic precautions; it is not even that time-consuming to maintain the latter.

[PatrickAlphaC]

Awesome post! Thank you!