The Problem with Resolutions

I guess you could technically claim that I didn’t fail at the resolutions I made earlier this year. The year isn’t over, however I believe that having long term goals such as these may be a bad idea. At this point, I believe that many of the resolutions I made [I.e. Learning R, meeting people who dealt with airline systems, and learning GridGain] may not be the best use of my time.

It might be a better use of my time to do periodical reviews of my current skillsets and recent tasks rather than to push forward blindly.

I’m not giving up on learning new things. I’m just not going to limit myself to a list.

Some of the technologies/tools I’ve been learning lately:

  1. OpenStack
  2. ArchLinux

Some technologies I would like to learn:

  1. Storm
  2. Ansible

5 thoughts on “The Problem with Resolutions”

  1. Long-term goals need to be more, well, “goalish” .. and not quite so “taskish”.

    Also, what does “learn R” mean? To be able to read and maybe update a program? To be able to do ‘something’ from scratch? To be able to write a compiler? That item, as an exemplar, needs much fleshing-out to be able to determine if you met it or not.

    For example, you might have a goal of eliminating credit card debt. Let’s say you have $30k racked-up that’s wracking you.

    That’s an awesome goal. But without measurable milestones, you’ll never get there.

    1. Well thats how I felt. It became more of a task list that wouldn’t change with the demands of my job and time.

Comments are closed.