My Hobbystreak

Disclaimer: This is Not My Idea

The concept of a hobbystreak is not something I have created and, in fact, has been around for a long time. I personally came across hobbystreaks following other people on Twitter as part of another hobby of mine. Mainly following Dana Howl (Dana Howl's Twitter account). Everyday she posts an update of a project she has on the go along with the hastags #HobbyStreakDayX and #Hobbystreak.

 The idea behind a hobbystreak is straightforward and there are two main parts to it:
  1. A small amount of effort everyday over a long period of time adds up
  2. The public record of social media helps to motivate you to keep it up

Why do This?

I have lots of failed and half started personal projects under my belt and lots of other projects that I want to do. I also have other commitments that I tend to obey and allow to rule my time rather than work on the things I'm passionate about. (Also, I procrastinate when I could be spending my time on something more productive). So, I'm starting this hobbystreak to help focus and motivate me to do the things I'm passionate about and complete them.

The Rules

The rules I'm going to follow for my hobbystreak (I have to once again credit Dana Howl for these rules - Dana Howl's Twitter account, and yes some of the below has been copied verbatim from one of her posts about this):
  1. Put at least 30 minutes of focused effort into my hobby each day.
  2. Post everyday on Twitter using the format: "#HobbyStreakDayX ....(content).... #HobbyStreak ....(other relevant hashtags)" along with a picture, and where X is the day of the hobbystreak
  3. Try to maintain the streak for as long as possible, if I miss a day I have to start back at day 1

What Constitutes my Hobby?

I don't want to limit myself as to what my hobby constitutes for the purpose of the hobbystreak. But it's going to be very heavily focused around:
  • data
  • data visualisation
  • data science
  • programming
  • technology
  • blogging
Also, I don't want to limit myself to having to be "generating content" for these hobbystreak days so a hobbystreak activity could be as simple as reading a book or listening to a podcast.

The End

Comments

Post a Comment

Popular posts from this blog

My First Year as a Data Scientist

Image
I was very fortunate to be given the opportunity by my employer to change role from a full-stack software developer to data scientist with the in-house Data Team. I've now spent over a year in this new data science role and thoroughly enjoy the different challenges it brings over software development. I wanted to write this blog post to firstly help me reflect on what I've been doing over the past year: what changes I had to undergo, what I did well, what I could improve on. And, secondly to help others in a similar situation to me - either thinking about transitioning or already transitioning by writing about some of the pitfalls and challenges I've had. Before I start, to elaborate on my background a little bit more: I haven't always been a software developer. I have completed both a Masters and PhD in Computer Science. So I didn't go into the move completely blind, I did have some previous experience of tools, models and methodologies to rely on. But I have a
Read more

PIVOT and UNPIVOT in T-SQL

Image
I recently passed my 70-761 Querying Data with Transact-SQL exam as part of mt revision I created the following diagram to help me remember how PIVOT and UNPIVOT work. I thought it would be good to share. For completeness, the following gives the syntax to use when using PIVOT and UNPIVOT. WITH PivotData AS ( SELECT <grouping column> , <spreading column> , <aggregation column> FROM <source table> ) SELECT <grouping column>, <distinct spreading values> FROM PivotData PIVOT (<aggregation function>(<aggregation column>) FOR <spreading column> IN <distinct spreading values>)); SELECT <grouping column>, <target names column>, <target values column> FROM <pivoted source table> UNPIVOT(<target values column> FOR <target names column> IN (<distinct spreading values>)); The End
Read more

My First Retro

Introduction A few days ago the opportunity came up for me to run a sprint retrospective for our sprint team. So I took the chance to try my hand at doing something a bit different. To give a quick bit of background to our sprint team. We have been trying to adopt agile practices for a while now but for one reason and another we have been quite slow in adoption of all the sprint practices we want to use. As such even though we have been "using agile" for over a year now, we have only had one sprint retro prior to the one I volunteered to run. Before I hosted the retro I read up (probably reading the same articles that everyone else reads after googling "sprint retrospective") and got the usual things about you cover "what we should start doing", "what we should stop doing" and "what we should continue doing". Rather than this being a rehash of these articles I wanted to talk about something different - the actual practicalities of
Read more