A year ago I set a few goals, much like the year before, and now it's time to review my results, also much like the year before.
Let's again begin with a scorecard:
Score: 1/5
I'd say I'm significantly better at typing, but I didn't invest the kind of concerted effort I intended, so no dice. I'd wager that at this point I'm close enough not to fret over it too much.
This most definitely didn't happen. I did better than in 2016, but mostly in the first few months of the year. I'm not really a blogger per se, so trying to force it results in quality below what I'd like for this particular platform.
Analysis paralysis was the biggest challenge here. I had spent so much time deciding between Elixir, Elm, and React that I ended up with nothing. On the plus side, I did toy around with all three a little bit, and it looks like in 2018 I'll get to do some of it at work, so all is not lost.
The one victory for 2016 was my understanding of Python. It's hard to put into words, but I feel much more in tune with the language philosophically. I'm not quite sure how much (more) expertise I have, but I feel like I understand what "pythonic" means far better than before, and that was the goal.
This was going reasonably well for a few months, but faded in the second half of the year.
Here's the list of released projects, in order of appearance:
import
sorting.All in all, I'm actually pretty happy with the results, as Autohook, Send Otter Love, Parsenvy, and Starminder have all been successes in their own ways:
I'll give myself partial credit for this one.
One (and a half) out of five is, uhh, definitely not great.
That said, 2017 was a big year for me personally, with my priorities and rhythm shifting throughout the year, so I'm OK with it. Additionally, the successful projects have far surpassed anything I've ever accomplished before on my own, which is a huge win.
In a few days I'll write up my thoughts for 2018. This time I plan on doing something different.
Thanks for reading! You can keep up with my writing via the feed or newsletter, or you can get in touch via email or Mastodon.