The #100DaysOfCode challenge is based on the standards developed at www.100daysofcode.com.
This repository will be used document my progress with this project.
If you have any questions about anything included here, please email me at firstname.lastname@example.org.
- The Rules
- My Goals
- Daily Learning
- Day 1-Day 2 - Add Matrices Challenge
- Day 2 - Bonus for Day 1 Challenge
- Day 3 - GitHub Projects - Day 2 Challenge Bonus - List Comprehension
- Day 4 - Create Bio Page - More List Comprehension - Other
- Day 5 - CSS - Blog CSS - Auto-formatting Python in VS Code - More List Comprehension
- Day 6 - Maintaining This Site - More List Comprehension - Hackerrank Challenges
- Day 7-8 - Hackerrank Challenges
There are two primary rules:
- Code a minimum an hour every day for the next 100 days.
- Tweet your progress every day with the #100DaysOfCode hashtag.
Truthfully, I don't think I'll be able to follow rule #1 (although I'll do my best), but rule #2 should be pretty easy to follow.
- Coding at work can't count towards your time.
- Your daily code should be pushed to GitHub. (The creator's proposed GitHub template can be forked from here.)
- Time spent on tutorials does not count. Only time spent working on challenges counts.
I'll be breaking rule #5, as I feel that learning (and coding) from video tutorials or books is still quite beneficial.
The template also mentions these additional rules which I will be following:
- Follow the 100DaysOfCode Twitter Bot which retweets all tweets with the #100DaysOfCode hashtag.
- Encourage at least two other people in the challenge on Twitter every day! Pay it forward!
Rule #7 will be an important one for me, as I'm developing a presentation on #100DaysOfCode where I will promoting the importance of the social benefits of this project.
In addition, I am adding this rule at least for myself, and I would encourage others to do the same:
- Write down your goals for this project! (see below)
The goals will of course vary over time, but at least it give me a direction to head in.
- This project isn't supposed to be about the tools you use to code, but I've wanted to learn Visual Studio Code for long time so I am going to do my best to use it exclusively for this project. In addition, I will document (and share) the beneficial things I learn about it.
- Again, about the tools... I will document everything using Markdown. Any tips I learn about Markdown will be documented here.
- I will also be sharing via my blogs (mostly beens.ca and beens.ca/python), which is something that I have seriously neglected lately.
- I will try to learn and adhere to Python's style guide, called 'PEP 8'.
- I have purchased a 6 month subscription to Python Morsels which offers programing challenges. I will likely start with that.
- I will share what I learned for each activity.
- I will compile a list of useful links that benefited me throughout this project.
- I will keep track of my more successful social media interactions related to this project.
- Explore how Projects work within GitHub.
- Do challenges from various sites, such as:
- Learn about PySimpleGUI.
- I noticed in another #100DaysOfCode participant's source code that he's using a library called
shelveas part of his file I/O. I'd like to investigate this.
- Learn how to use machine learning to adapt aircraft performance charts into a program. (To go along with my flying and ground school lessons.)
- Flutter looks very cool for app development. This is a lower priority that I might not get to in the 100 days of this challenge.
- Create a Twitter Bot.
- More to come...
Day 1-Day 2 - Add Matrices Challenge
I will start with the 'Add" challenge from Python Morsels:
Write a function that accepts two lists-of-lists of numbers and returns one list-of-lists with each of the corresponding numbers in the two given lists-of-lists added together.
Day 2 - Bonus for Day 1 Challenge
Sadly I don't have the list comprehension skills needed to do this challenge properly (read: Pythonically) so I'm pursuing some list comprehension exercises to do.
I've also learned that creating the TOC on Markdown pages like these has limitations with the characters that can be used in the headings).
Day 3 - GitHub Projects - Day 2 Challenge Bonus - List Comprehension
I poked away a little at the day 2 challenge bonus but it's turning out the be......a challenge! I've decided I wanted to learn more about list comprehension before I continue with this.
I spent quite a bit of time on a Python notebook I created to learn about list comprehension.
Day 4 - Create Bio Page - More List Comprehension - Other
Today I reinforced my list comprehension skills, created a bio page on GitHub Pages, and learned more about the limitations of creating a TOC in Markdown.
Day 5 - CSS - Blog CSS - Auto-formatting Python in VS Code - More List Comprehension
Today I edited the CSS on my website, learned how to auto-format my Python code in VS Code, and got my day 2 challenge close to being complete by learning more about list comprehension.
Day 6 - Maintaining This Site - More List Comprehension - Hackerrank Challenges
I spent some time re-thinking how I process this site. I had too much duplication going on but hopefully now I can be more efficient with writing up my activities and progress.
I finished the 1st bonus section the day 2 challenge thank to what I was able to learn about list comprehension.
I started working on challenges from the Hackerrank website.
Day 7-8 - Hackerrank Challenges
Today I reinforced the basic data types including lists, dictionaries, and tuples by completing a number of Hackerrank challenges.