Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles / web / CSS

2020: The Year of Data

3.00/5 (1 vote)
27 Dec 2020CPOL5 min read 2.9K  
In this post, I will continue the tradition which I started in a 2015 blog post of celebrating the year and looking back at highlights.

This article appears in the Third Party Products and Tools section. Articles in this section are for the members only and must not be used to promote or advertise products in any way, shape or form. Please report any spam or advertising.

2020: The Year of Data

I’ve always been happy to share that I embrace change and take on new challenges every year. I started the tradition of celebrating the year and looking back at highlights in a 2015 blog post. This year, I will continue that tradition. Despite the challenges and struggles of 2020, I am hopeful for the future and optimistic about the changes to come. Last year also impacted me in personal ways that inspired me to launch a separate blog.

For my post summarizing 2019, I began by sharing statistics about the exotic locations I traveled to and reflecting on 25 years of professional development. This year, due to the pandemic, the theme was exploring the Pacific Northwest. I also made a major career move early in 2020 and wrote about my new role as Senior Program Manager for .NET Data. That checked one of my major goals for 2020. My mission for several years has been:

Empower developers to be their best.

As a program manager, I continue that mission by helping steer the direction of products to address the greatest needs of the developer community.

My other goals were mostly personal, and I reflect on those and share my personal journey in a separate blog post: 2020 Couldn’t Shake Me.

My Goals for 2021

I have many goals for 2021 and shared my personal ones my other blog. These are my technology-related goals for 2021.

  • Continue to advance my career at Microsoft. My goal is to become a principal program manager.
  • Resume my news feed of daily relevant updates shared on social media.
  • Help the EF Core team release EF Core 6.0.
  • Raise awareness and increase adoption of .NET for Apache Spark.
  • Understand and implement what’s needed to make a great GraphQL story for .NET developers.
  • Support local user groups around the world through virtual presentations.

Open Source

I had more open source contributions in 2020 than 2019, which was also more activity than 2018 and 2017.

GitHub 2019 Activity

GitHub contributions in 2020

The increase is due to my active involvement with the EF Core team and taking on a major side project with Expression Power Tools.

Twitter in Review

My followers grew from 13,102 in 2019 to 15,101 this year. That’s a 15% increase and slightly higher than my growth in 2019 (up from about 4 followers per day to 5). I assume that’s mostly due to my association with the EF Core and .NET for Apache Spark teams. The more important number, engagement, was way down. I attribute that mostly to consistency: I stopped regularly posting relevant news items and was more reactive with product-related tweets. It’s my goal to change that in 2021, so if you were following me to stay abreast of the latest in the .NET world, I’ll be back!

As always, the following stats are based on the last 90 days.

Demographics

Twitter removed the dashboard for demographics information in early 2020 and I don’t use 3rd party tools to analyze these, so I have no updates here.

Top Tweets

The most impressions for any tweet this year was a reference to a blog post I wrote about how to connect to Azure Cosmos DB directly from a Blazor WebAssembly client.

My top mention was a tweet by the official .NET Twitter that featured a blog post of mine about how to inspect and mutate IQueryable expression trees.

Finally, the top “media tweet” was a post announcing the open source Windows Package Manager, winget.

That’s a wrap for social media. Let’s look at my blog.

Developer for Life in Review

Last year was the first year I did not move my blog to a new platform. I wrote about migrating from Medium to Hugo and have continued to update my Hugo version and use CI/CD o build and deploy it.

Last year, I received 96,047 visitors over 123,961 sessions, about a 30% increase from the previous year.

This year dropped to 61,930 visitors over 84,376 sessions. In my new role and with my focus split between two blogs, I simply did not write enough fresh content to drive new traffic. I don’t have a goal for visitors or sessions, but I do have a mission to empower developers and blog posts are a big part of that. I will do more in 2021. Almost three-quarters of incoming traffic is from organic search.

Acquisition for Developer for Life in 2020

Over half of my traffic came from organic searches. The top 10 search phrases covered three broad topics: Blazor, JavaScript, and a one-off blog post I wrote in 2018 that explains how to run MongoDb in Docker on Windows.

The top three third party referrals came from GitHub, a case study of my site published on JAMStack.org, and The Morning Brew.

Because I did not post as much news, I did not use my link tracker as much so I’m skipping statistics for that. I will likely retire the link shortener in 2021 and just post direct links.

Closing Thoughts

Looking back at previous years, technology trends I identified include:

  • 2017 Docker and Serverless - package and scale your code
  • 2018 .NET Core - build your code for any platform
  • 2019 WebAssembly - target one platform that runs everywhere

2020 was the year of .NET data for me. My new role exposed me to EF Core and .NET for Apache Spark along with technologies like gRPC and GraphQL. Last year, I said 2020 would be the year that “WebAssembly and modern JavaScript truly shine.” I haven’t been plugged into the modern JavaScript world, but Blazor has certainly taken off with the WebAssembly version gaining a strong foothold. I don’t know what the “big thing” for 2021 will be overall, but I do know what I will focus on: making data access as great as it can possibly be for .NET developers.

See you in 2021.

Jeremy Likness

 

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)