create a repo for 100 Days Of Code Challenge

Author: kallaway

FAQ.md

@@ -0,0 +1,38 @@
+## FAQ:
+  **Q:** How do I get in touch with the people who are also doing this challenge?  
+  **A:** Search for #100DaysOfCode on Twitter, or join [the 100DaysOfCode room on Gitter](https://gitter.im/Kallaway/100DaysOfCode) — you don’t need an invite, it’s open for anyone to join. Also, follow [@_100DaysOfCode](https://twitter.com/_100DaysOfCode) on Twitter to stay in touch with the community.
+
+  **Q:** I've already started the challenge, and I'm currently on Day 8. How can I start using this repo to track my progress?  
+  **A:** Don't worry. Restore as much info on the previous days, but if you can't then just continue from where you are right now. If you have been tweeting about your progress every day, put the links to your tweets in the Log for each day. Then, follow the format.  
+
+  **Q:** I am new to coding (or just deciding to learn to code) and can’t build projects yet, what should I do?  
+  **A:** The best way to start would be to follow the [FreeCodeCamp’s Front End Curriculum](https://www.freecodecamp.com/) from the very beginning. The further you get during the 100 days, the better.  
+
+  **Q:** I’ve missed a day, does it mean I’ve failed the challenge?  
+  **A:** Absolutely not. You are allowed to miss one day (then make it up by adding one more day to the end of the 100), but never miss two days in a row. This is a great piece of advice on habit formation that I got from Leo Babauta at zen habits.  
+
+  **Q:** I come home late, and by the time I am finished with my hour, it’s past midnight, does it count?  
+  **A:** Of course it counts! The rule of thumb is: have you coded for at least an hour before going to sleep that day? If yes, you are on track.  
+  The reason for this is that we all have different schedules and different life periods (kids, school, work, and what have you) so don’t hold yourself to some arbitrary time standard. You will not experience what Cinderella experienced once the clock strikes midnight.  
+  Don't worry whether you get a point on GitHub on that particular day. Yes, it’s nice to have them in a streak one by one, but don’t do yourself a disservice by measuring your efforts to a clock.  
+
+  **Q:** Should I keep a journal?  
+  **A:** Yes you should, and the best way to do that is to fork this repo, and commit to [the Log](log.md) daily. It’s helpful in two major ways: you will be able to look at the progress each day and see how far you’ve already come and it will be easier to find the motivation to continue, and the second one is that after you’ve done your 100 days, you will be able to analyze your experience better and see what worked and what didn’t.
+
+  **Q:** Should I put my projects online?  
+  **A:** Definitely. It’s great for accountability and motivation to know that the stuff you’ve worked on is accessible online to anyone who may wish to look at it. It will make you care about the end product more, and will lead to a more impressive result in the end. I suggest you put them on GitHub.
+
+  **Q:** Should I worry about streaks?  
+  **A:** Streaks are nice and helpful, but as I mentioned above — don’t worry about them too much and don’t criticize yourself over missing a day. Instead, make sure you do everything to not let that happen again, and know that worrying and scolding yourself will not give you any results. (Ok, It will give you results, but only negative. I would call them consequences, not results) The best way to get out of that negative emotional state is to sit down and code.
+
+  **Q:** What is the most difficult part of this challenge?  
+  **A:** The part where you have to sit down and start coding. Don’t postpone that or think about it at all, because you will rationalize yourself out of it. Approach it mechanically: sit down, open your laptop, launch your coding editor, and start typing. After 5 minutes, you will not feel any problems/procrastination/desire to stop.  
+
+  **Q:** If everyone started on a certain day, should I join them on the day they are? For example, from Day 12?  
+  **A:** This challenge is individual, so when you join you start at day 1. Whenever you’ll be posting an update on Twitter or elsewhere, make sure to mention which day you are on and use the hashtag so that people can find and support you!  
+
+## Contents
+* [Rules](rules.md)
+* [Log - click here to see my progress](log.md)
+* [FAQ](FAQ.md)
+* [Resources](resources.md)

README.md

@@ -0,0 +1,21 @@
+# I've joined the #100DaysOfCode Challenge.
+
+## Contents
+* [Rules](rules.md)
+* [Log - click here to see my progress](log.md)
+* [FAQ](FAQ.md)
+* [Resources](resources.md)
+
+## If you've decided to join:
+1. Fork this repo.
+2. Read this: [Join the #100DaysOfCode](https://medium.freecodecamp.com/join-the-100daysofcode-556ddb4579e4)
+3. Code minimum an hour every day for the next 100 days.
+4. Fork this repo and commit to the [Log](log.md) every day.
+5. Change the date in [Rules](rules.md) to the day you've started the challenge.
+6. Delete the examples in the log, or comment them out, and start filling it with your own content.
+7. Tweet your progress every day using the #100DaysOfCode hashtag.
+8. Follow [100DaysOfCode](https://twitter.com/_100DaysOfCode) Twitter Bot that retweets all the tweets that contain the #100DaysOfCode hashtag. It's a great way to keep yourself motivated and to participate in the community. Thanks (@amanhimself)[https://twitter.com/amanhimself] for creating it!
+9. If you find a great, helpful resource that others would benefit from, either submit a Pull Request to add it to the repo, or just tweet at me (see info below)
+
+## Note
+* If you have any questions or ideas about 100DaysOfCode (or other ideas), feel free to reach out to me on Twitter: [@ka11away](https://twitter.com/ka11away)

log.md

@@ -0,0 +1,30 @@
+# 100 Days Of Code - Log
+
+### Day 0: February 30, 2016 (Example 1)
+##### (delete me or comment me out)
+
+**Today's Progress**: Fixed CSS, worked on canvas functionality for the app.
+
+**Thoughts:** I really struggled with CSS, but, overall, I feel like I am slowly getting better at it. Canvas is still new for me, but I managed to figure out some basic functionality.
+
+**Link to work:** [Calculator App](http://www.example.com)
+
+### Day 0: February 30, 2016 (Example 2)
+##### (delete me or comment me out)
+
+**Today's Progress**: Fixed CSS, worked on canvas functionality for the app.
+
+**Thoughts**: I really struggled with CSS, but, overall, I feel like I am slowly getting better at it. Canvas is still new for me, but I managed to figure out some basic functionality.
+
+**Link(s) to work**: [Calculator App](http://www.example.com)
+
+
+### Day 1: June 27, Monday
+
+**Today's Progress**: I've gone through many exercises on FreeCodeCamp.
+
+**Thoughts** I've recently started coding, and it's a great feeling when I finally solve an algorithm challenge after a lot of attempts and hours spent.
+
+**Link(s) to work**
+1. [Find the Longest Word in a String](https://www.freecodecamp.com/challenges/find-the-longest-word-in-a-string)
+2. [Title Case a Sentence](https://www.freecodecamp.com/challenges/title-case-a-sentence)

resources.md

@@ -0,0 +1,24 @@
+# Recommended resources
+
+## Helpful Articles
+1.
+
+## Projects and Ideas
+1. [FreeCodeCamp](https://www.freecodecamp.com)
+2. [The Odin Project](http://www.theodinproject.com/)
+
+## Other resources
+1.
+
+## Tools
+1.
+
+## Books (both coding and non-coding)
+1. "The War of Art" by Steven Pressfield
+
+
+## Contents
+* [Rules](rules.md)
+* [Log - click here to see my progress](log.md)
+* [FAQ](FAQ.md)
+* [Resources](resources.md)

rules.md

@@ -0,0 +1,28 @@
+# Rules of the 100 Days Of Code Challenge
+
+## Main Commitment
+### *I will code for at least an hour every day for the next 100 days.*
+
+#### Start Date
+June 25th, 2016. [PUT YOUR DATE HERE]
+
+## Additional Rules
+1. I will tweet about my progress every day -> using the hashtag #100DaysOfCode
+2. If I code at work, that time won't count towards the challenge.
+3. I will push code to GitHub every day so that anyone can see my progress.
+4. I will update the (Log)[log.md] with the day's progress and provide a link so that others can see my progress.
+5. I will work on real projects, facing real challenges. The time spent doing tutorials, online courses and other similar resources will NOT count towards this challenge. (If you've just started learning to code, read [FAQ](FAQ.md))
+
+
+## Ideas to make this challenge more effective
+1. To increase the chances of success, it's a requirement that you add a link to each of the day posts in the [log](log.md). It can be a link to a commit on GitHub, a link to a blog post
+2. If you get upset or stuck, read this article: [Learning to Code: When It Gets Dark](https://medium.freecodecamp.com/learning-to-code-when-it-gets-dark-e485edfb58fd)
+3. If you don't know why there is such an emphasis on working on the projects vs doing tutorials or online courses, read this: [How to Get a Developer Job in Less Than a Year](https://medium.freecodecamp.com/how-to-get-a-developer-job-in-less-than-a-year-c27bbfe71645)
+4. If you can't push your code to GitHub for some reason (e.g. if you're only starting to code and doing interactive exercises), provide a link to a tweet. You can think of something else as long as your challenge stays public - and you get the benefit of being committed to it and accountable for your progress.
+5. Another good bonus of forking this repo -> if you haven't worked with Markdown before, it's a good way to practice.
+
+## Contents
+* [Rules](rules.md)
+* [Log - click here to see my progress](log.md)
+* [FAQ](FAQ.md)
+* [Resources](resources.md)