100 days

There are a lot of challenges shared on/to social media. You’ve probably seen them. Write a blog post daily for 10 days. Or post a picture you’ve taken daily f0r 30 days. Depending upon your devotion, these can be easy or difficult to go the distance.

In the program for the Bring IT, Together Conference, Peter Beens offered a session about 100 Days of Code. Not 10 days; not 30 days; but 100 days. This was like waving a red flag in front of me. I had to check it out.

The session was small which made for an intimate discussion with Peter.

So, off we went. Peter’s presentation resources can be found here.

I went to the session with a particular interest to finding out what Peter was learning about coding and how he found the inspiration to stick with it for the 100 days. He kind of headed away from that discussion by pointing out that, while the process was based on https://www.100daysofcode.com/, the key to success was to make it personal. He had bought into that concept which was the major takeaway from the session, not what he had done personally. I’ll buy that and in the slidedeck, you’ll find some of the challenges that he undertook.

He also encouraged us to think bigger. I found that interesting; use the concept but apply it to something that you’d like to pursue.

Using this approach, he offered these suggestions…

There were a couple of things that he demonstrated that I know that I need to do more and then there are a couple of things that have been nagging me all along that I haven’t addressed properly.

  • of course, the coding. I need to find projects of personal interest and code for more than random things every now and again
  • I do have a GitHub account, but I need to do more with it. Something Peter mentioned of note that really resonated was the more readable links for sharing
  • I’ve always meant to look into GitHub as a blogging platform. Mike Zemansky demonstrates this well with GitHub pages. https://cestlaz.github.io/
  • investigate GitHub for use in the classroom

These are not quick and easy things to address and I don’t see them coming to fruition any time soon.

But, we all need inspiration to move and keep learning. Peter provided that inspiration for me in this session. Thank you, sir.

Author: dougpete

The content of this blog is generated by whatever strikes my fancy at any given point. It might be computers, weather, political, or something else in nature. I experiment and comment a lot on things so don't take anything here too seriously; I might change my mind a day later but what you read is my thought and opinion at the time I wrote it! My personal website is at: http://www.dougpeterson.ca Follow me on Twitter: http://www.twitter.com/dougpete I'm bookmarking things at: http://www.diigo.com/user/dougpete

3 thoughts on “100 days”

  1. 100 days of code – I love the idea. I don’t spend as much time writing code as I would like. Mostly I am writing code for use in class and that doesn’t take that long. Student projects are easy for someone who has been coding for decades. I have some things I want to do for my own interest but finding time and motivation is hard. Maybe when I retire in the spring.

    GitHub is very interesting and I spent some time with it this summer hoping to use it with students. I found that what I wanted/needed to do was somehow just very confusing for me. I need lessons. Even the videos and book I bought just didn’t seem to help me enough. Maybe I’m old or something but the pain was not worth the gain. I had a very simple way of distributing projects to students and decided to just use that. I’d like them to learn GitHub not I need to learn it myself first.

Comments are closed.