It’s strange to be back to work on a Monday, with kids still in the house (they start school tomorrow), after being gone for the last 10 days from work. It was really gone, as I didn’t process email or mess with work in any meaningful way. I did clean some spam over vacation when others were gone, and I added a few Database Weekly links last week, but I didn’t check SQLServerCentral, edit articles, or do anything really SQL related.
About the only computer tasks I’ve done since the day before Christmas were a few hours on the Advent of Code stuff I’ve been working on in my spare time, and even that was minimal. I got stuck on a few puzzles, and didn’t have much time to work through them. I’d give it 20-30 minutes, but then break for family time.
It’s a new year, and I’m starting slow. At least slow this week as I take stock of the publishing queues and start to plan how I’ll proceed forward. As I left last year, there were a lot of new technologies coming from Microsoft in 2016 that I felt I needed to get up to speed on. Some are out, some coming, but they’re a point of emphasis. Like Buck Woody with his Data Scientist work, and Grant Fritchey with R, I’m proceeding to learn more about analytics, including data lakes and statistics, as I move through the year. Particularly I’m focused on Python as the language to use, though from what I see with R, lots of the same libraries and formulas apply.
I’m also looking to continue forward with the #SQLNewBlogger posts and see if I can inspire some of you to move forward with your own skills and thoughts on how SQL works for you. I’m going to look to get at least 2 posts a month out here, and perhaps more.
Travel starts quickly, with a week long trip to the UK in two weeks and then SQL Saturday Austin, but other than that, it will be a light quarter for me. Just one event in Feb, and none in March. I am looking forward to that slow beginning.