There are plenty of coding challenges floating around the internet.  But, a lot of them are in spaces that feel highly academic (I dropped out of college twice) or are based on competition.  I wanted to participate in a coding challenge that was based on completing a project, watching other people complete projects, and celebrating the fact that we’re all making progress at the same time.  I find it really interesting to see how people approach problems, and what they learn from “failures”.

I also knew that I didn’t want to commit to a long-term coding challenge. I write code for a living, so I’m already putting in at least 8 hours per day.  I know myself well enough to know that if I committed to a long-term coding challenge, my self-care wouldn’t be a priority.  And to be perfectly honest with you, when my self-care isn’t a priority, my life just kind of falls apart, so…. I’m not interested in that.

I’d also have to give up some time exploring Portugal and Spain.

No thanks!

So, I took the things I liked about coding challenges and pulled them away from the things that I don’t like.  Here is what I came up with:

  1. The challenge will be 5 days.
  2. You should spend at least an hour on the project.
  3. We recognize that planning, prepping, and learning are all parts of the project.
  4. This is a great opportunity to wrap up unfinished projects, learn a new language, or dive deeper into an existing one.
  5. We’re going to document our wins, frustrations, victories and “failures” in Slack.

If you want to join us, the first coding challenge starts Monday, September 25th.

See you in Slack!

UPDATE

I’m thinking about making this a weekly thing!

Also, if you haven’t noticed, I’m going through each blog post, reading them, and following up with commentary.  So, if Audio is your thing…

 

Leave a Reply

%d bloggers like this: