That was 2018, So Here are Goals for 2019

Usually we here some degree of “the year was fun” or “screw this year, and next will be better.” On the surface, the engagement and the house made for a pretty outstanding year. Also, I got a volunteer promotion in the late fall as the Vice Chair of the ASNC Human Rights Committee, adding a little more responsibility on site visits and ensuring plan reviews are completed by the right members. However, this also took enough time that a lot of intended professional and running goals fell by the wayside.

Last time I wrote a blog for a T-SQL Tuesday concerning 2018 goals, it was a public goal accountability type of post in terms of learning. So what was accomplished (struck from the record)?

  • MBA Program and ITIL: finally graduated in December, and got a certification. Both check.
  • DBA fundamentals focus: well, this is subjective, but I think I reached this goal through some simple blog learning and shadowing some DBAs. I think I gained a better understanding on keeping backups and even temporal tables. I’ll call it a win for now.
  • Mid-level Python and mid-level R development: my focus was more on architecture, so this got scrapped.
  • Two new talks: I had one, though it will continue to mature. Got to discuss normalization and took it on the road (yet never published the blog, which I was terrible at this year). However, I didn’t devote time to consider a second to add to my rotation of…three. Still figuring out the presenting benchmarks.
  • Set up a true home lab and my own database: never got the data I wanted in full, and didn’t try. Or maybe I was afraid of all the XML files I created without trying JSON instead. Big miss anyway.
  • Get reacquainted with MySQL: I’ll call this one a win because of a server I dealt with that used MySQL. Very generalized, but I got to check the nuances between PL/SQL and T-SQL again.

So last year was unsurprisingly too ambitious on the professional front. However, it’s time to try 2019 again, even if I did not publish this post until February.

To start, my first goal is the most important: do well in year one as a first time husband. My start date is April 20. I hear the manager was also expecting a lifelong commitment to the craft.¬†With that in mind, this means I want to be cautious as I continue in my career to not try for too much. I write this because data is more than a job to me, but there’s a matter of still enjoying it while making time for other fun things in life.

Now this year’s professional goals.

  • Actually make that custom database happen: I want to make my home lab actually look like something worth demoing, which means I should consider the test database I use needs to be a heck of a lot more robust, and I don’t want to be using World Wide Importers a ton. So that racing database which I want to more fully design is where I will start, which will require some creative thinking when I talk to the timers…or to the company behind the prediction algorithms.
  • One new talk to speak on: after not meeting last year’s goal of two, I would rather focus on tweaking the current ones when I have time in addition to adding a new topic for both my own growth and because I was told that my topic idea was rather good as many others have asked this same question in the early days of their jobs/assignments. May start that one with a blog post this time, so no more details…yet.
  • Speak to a new audience, whether it’s a specialized user group locally or even outside the Triangle: I’m hoping that any of those talks can be presented outside of my work environment or my SQL Server community, as I’d like to change up the audience for my own growth. It likely depends on the subject on if I can speak at a group with another language as the focus, whether it is a bunch of analysts who are beyond my pay grade when I was an analyst, or the .NET developers I yell at when they develop bad SQL code and haven’t learned from my own mistakes (I don’t yell; I just quietly facepalm).
  • Learn SQL to JSON integration techniques: so this is something I will need in my next adventure; I will get to that in a separate post. Considering that the only character that likes XML file imports is No One Ever, I think transitioning to JSON could be smoother, but someone will try to fight me over it.
  • (Re)start the MCSA certification exam (stretch – get the certification): time to get back to something I started and then let expire. The database development exam structure has changed since, and I feel more prepared for both exams. This does¬†not mean I finish the exams and get my cert, but I officially train and possibly complete one exam with the intent of the next one not long after.

Hopefully this is a bit more reasonable than the previous year, as now we’ve found a groove as homeowners. So now it’s time for my other major extracurricular activity outside of my career industry…the one where I use my feet a lot.

I did run more miles than the previous year, though it’s not because the last eight months were something outstanding. I had a goal of 1500 miles and missed even hitting 90% of that. My excuse is that I was burnt out after the Shamrock Marathon training cycle and subsequent race ended with a thud. The miles dropped because the desire was lacking, especially as a house and the final stretch of my MBA pursuit took priority. On the good side, I did have half marathon, 10k, and mile personal bests.

For 2019, I want to get back to a spot I was in when it came to endurance versus speed.

  • 1500 miles on the year: I’m going to start an actual training plan which uses some algorithms to create a plan. It’s less than $100 annually, so I can squeeze it in to personal expenses outside the household ones. I believe many of us hobbyists also have a similar mentality to pros and semi-pros that when it comes to miles, we wish to ensure that they count for something.
  • Run my third marathon and break 4:00 (stretch – 3:35): I had this goal for Shamrock and then mile 18 is where everything fell apart. I’m not at a Boston level as some of my friends are, but I think if I put in the work at something I love, this can work. Also not hoping to get a stomach bug in the days heading into the race; that would help.
  • Run a 5k at a consistent sub-6:40 pace (stretch – break 20 minutes): I am a sadist who likes to run fast (for me), though I am very mediocre at my fastest. After I smoked the Rocket Mile last year, however, I’ve found algorithms which predict 19:30 when running on an even course (a rarity). Again, the plan combined with the algorithms (and badgering their data scientists if I’m crazy) would tie into learning more data science techniques if I give myself free time.
  • Racing at least once every 8 weeks at a minimum, and four times in the same span as a maximum: this will be interesting, as that means I need to watch what summer races I select. Charity type is a priority, especially with my likely return as Triangle RunWalk for Autism competitive ambassador.

Data growth is important to me, as is my running stress therapy. So let’s see what 2019 brings after this stream of consciousness entry. Any tips on the realism of the goals or where to begin?