2022 is over, and not a moment too soon. I'll never forget it: some of my friends had to flee their own country; others are fighting for their freedom as I write this post. I hope they will be safe and that their wishes will come true in 2023.

On the personal and technical side, here's a summary of the past year from my perspective.

Job change

First and foremost, I changed jobs. I worked for Hazelcast for 3½ years. However, I started to become dissatisfied with the company's direction and my position within it. I looked for a couple of months for my next gig. In February, I started to work on Apache APISIX:

Full Lifecycle API Management API Gateway, Ingress Controller, etc. Apache APISIX provides rich traffic management features like Load Balancing, Dynamic Upstream, Canary Release, Circuit Breaking, Authentication, Observability, etc.

When I joined Hazelcast, I had to understand distributed systems and concepts related to them: clocks, order, split brain, leader, etc. In comparison, an API Gateway such as APISIX is pretty simple. Hence, my focus is more on learning underlying technologies:

• NGINX
• OpenResty
• Lua
• Kubernetes
• Ingress
• etc.

It means I had to shift the subjects I write about: you won't find any Java and hardly any Kotlin.

My blog

In 2022, I published 50 blog posts on https://blog.frankel.ch/: one each week on Sunday, but on Christmas and the New Year - for obvious reasons. Here are the top 5 most viewed pages:

Two things are of interest:

1. The 4^th most viewed page is the homepage
2. The 5^th, about cache providers, was published in October 2021. It's a long tail, indeed!

Views are broken down as the following during the year:

You can notice a couple of huge spikes. They are Hacker News front page occurrence. I advertise on HN when I believe the post has potential; sometimes, others do. Most viewed posts correlate somewhat with referrals from Hacker News.

Cross-posting

2022 also saw consistent cross-posting on third-party content aggregator sites, which allow linking to the original post. As a reminder, Google (and other search sites) flag similar content as duplicate. If the aggregator site has more "page rank" than your site, then the content on the latter will be marked as such. The rel canonical attribute is the way to tell Google: here's the original content, don't flag either as duplicate. I only post on sites with such a feature.

That being said, here are my followers depending on the site:

• Medium: 564
• Dev.to: 1,838
• Hashnode: 80
• DZone: no follow feature
• Hacker Noon: no follow feature
• foojay.io: no follow feature either

It's interesting to see that though I thought dev.to focused on web and front-end, I got many followers though I rarely write on such subjects. Conversely, I still need to understand why my follower base on Hashnode doesn't take off.

Public speaking

Indeed, 2022 was not my best year in terms of conference attendance. Here's a comparison of the previous years:

Raw numbers are a bit misleading: Because of Covid, I spoke at many events online in 2020 and 2021. It's much easier to do so than traveling to another country (or continent!); on the other hand, engagement is much lower, not to mention the lack of social interactions.

Anyway, 2022 numbers are below 2019's, the last "regular" year. Despite this, I'm ok with it: 2019 was hard on me, and conference attendance is more of a marathon than a sprint. I think I've found the sweet spot between public speaking and other activities.

Regarding content, I mainly did two talks:

1. Evolving your APIs
2. Chopping the monolith

It's below the number of talks I usually try to achieve, but they were pretty popular, especially the first one. I'm working on more diversity for 2023.

GitHub contributions

As a Developer Advocate, my GitHub contributions are different from the ones of a regular software developer, especially one working on Open Source.

Most of my contributions are commits because I'm the only one working on my demos. Furthermore, I regularly update them with the latest version of whatever dependency I use. I'm trying to open issues on Apache APISIX since I'm a huge user. Eating one's dog food is a great way to uncover either bugs or usability improvements. Finally, pull requests are for blog posts and reviews for my colleagues' blog posts.

Conclusion

Years when one changes jobs are always challenging but very interesting; 2022 was no different. My resolution for 2023 are:

• To deepen my understanding of the Apache APISIX ecosystem
• Write as many blog posts as in 2022 - it's hard to do better, anyway
• Design at least three new talks

What are yours?

Originally published at A Java Geek on January 8^th, 2023