Had a lapse in my #100DaysOfCode since my computer crashed & was in the shop. Tried coding some days by hand for an hour (highly recommended!), but I'll be restarting the challenge tomorrow with day 1. More eager the second time around given the progress I've already seen.
Day 15 (yesterday): The hardest day yet since, in the middle of working, my computer crashed. It's in the shop, but it didn't stop me. I bought a dry erase board and have been writing code on that. That counts right? It should count. Let it count ๐ #100DaysOfCode
Day 14 (Catching up on tweets): Continued with my yatzy game in Python, creating and playing with classes and making new methods for dice rollers. #100DaysOfCode
Day 13 (Catching up on tweets) : Began a @treehouse project for creating a game of yatzy in Python. Got a little stuck in understanding OOP, but found some resources on line to practice and sink my teeth into #100DaysOfCode
Day 12: Practiced more OOP in Python...Something I thought I understood well yesterday, now seems very confusing. Wondering if it'll ever make complete sense. Baffled by how programmers apparently keep so many rules in their head. But onwards, nonetheless #100DaysOfCode
Day 10 - pretty much just reviewed and re-ran everything I learned on day 9 since it's thanksgiving, but nonetheless found the hour to code. #100DaysOfCode
Day 8: More Object-Oriented Programming through #Python. Was suggested this helpful @YouTube video series by Corey Schafer which made OOP easier to digest. Highly recommended if you're diving in & trying to wrap your head around OOP logic #100DaysOfCode: https://t.co/tT9X274SoW
Day 4: Finished and submitted a @treehouse project. Filled out more of my @github profile. Read about version control systems and started working on my next project. #100DaysOfCode
Day 3: Fell in love with @pycharm. Fine-tuned and made good progress on a @treehouse project that I've been struggling on. Read a lot on python comprehension. And began my journey into the deep waters of @github and Git. #100DaysOfCode
Day 2: Spent a couple hours reading about and practicing positional arguments, *args, and **kwargs. Made promising progress on my own project by dissecting and interpreting comparable projects on @github. Learned more about when to use #python sequence slicing. #100daysofcode
Day 1: Spent hours on a project from @treehouse only to realize I was not on the right track after getting feedback. Spent the rest of the day stressing and pulling out my hair in frustration for not being able to do a python project without handholding. #100DaysOfCode