We appreciate your thoughts.

Thank you for providing us with your highly valuable feedback. We appreciate the time and thoughts you put into these feedbacks. Your feedbacks contribute and help grow this site. The information below are just suggested thoughts to keep in mind and options in which you can provide them.

Possible Questions and thoughts to keep in mind when providing feedback.

Here’s a list of question you may want to keep in mind when providing a feedback of the tutorial/lesson that you are using.

  1. Does the tutorial/lesson prepare you as far as what software/program was needed?
  2. Does the tutorial/lesson inform you on how much experience or how familiar you should have with the software/program you are using the guide for?
  3. Does the tutorial/lesson provide an easy to follow layout?
  4. Does the tutorial/lesson seems too long or to short?
  5. Was it organize and were you able to find the object/information you needed in a timely manner?
  6. Does the tutorial/lesson provide a reason or concept on how said lesson compares to similar lesson?
  7. Does the tutorial/lesson suggest how it could be applied other work?

Different options/method or ways to provide feedback.

1. PierceHacker contact information via email or tweet.

Please contact our PierceHacker team leader at Jason’s emial or tweet us at Twitter if you have any question, issue, or recommendations with any of our tutorial/lesson or the site itself. A brief description in the subject line of the email/message will help speed up the response time.

2. Reporting an issue via GitHub.

This method will get the fastest response. This method allows all of the PierceHacker team to see and respond to your issues. Using this (link) will bring you to a template which you can use if you choose. This GitHub link will take you to the Pierce-Hacker-Submission webpage.

3. Making a detail suggestion.

This method/option will allow you to leave detail comments to specific lines within the tutorial/lesson in our directory. The PierceHacker team will then read and take your suggestions into consideration.

4. Pull Request for access to the file.

If you feel that you’re experience and familiar with GitHub and markdown files, you can make a pull request and edit/fix the tutorial/lesson yourself. You’ll make changes to the current version and submit them. Our PierceHacker team will then review the changes and decide if they should replace the current tutorial or lesson.