Looking Back at 2024

Let’s continue last year’s tradition and look back at my personal highlights of 2024. I’m looking back at a year that was unusually busy and intense but full of blissful moments, meaningful connections, healthy change and new challenges. Luckily I had some generous vacation time, allowing me to catch a breath and making sure I don’t drown in the chaos.

In October ‘24 I caught these stunning northern lights in our neighborhood on a late walk home.

Once more, this post is long. I didn’t bother cutting it short as this is my chance to self-reflect and tell a story. Here’s a handy table of contents if you want to skip some of the boring sections. I won’t notice.

• 💻 Work
• ☀️ Leisure
• 🎓 Learning
• ✨ Pet Projects
• 💪 Health & Exercise
• 🗺️ Travel
• 🎸 Music
• 📚 Books
• 🍕 Cooking

Work

My professional life saw a lot of changes in 2024. At the beginning of the year I was a Principal Software Engineer at Stack Overflow and worked on strategic and longer-term architecture topics that impacted the entire engineering organization at Stack. I worked on topics like moving out of our data center, establishing a multi-cloud strategy, moving away from an aging monolithic application architecture towards a modular monolith, and enabling teams to build, maintain, and operate microservices on their own. I ran our architecture guild and tried to foster a culture where all engineering teams can have more autonomy and ownership over the software they’re building. It was an interesting role that allowed me to do a lot of research, spike solutions, work on the longer-term strategy of our engineering department, collaborate closely with our engineering managers and our CTO and learn a lot about running a healthy engineering organization. I learned a ton in this role and loved the autonomy I had.

On good days I could really see how the things I did had a fundamental impact on the entire engineering organization. On bad days, however, I felt out of touch with the rest of our engineers. Focusing on longer-term strategy, fundamental research and leadership left me longing for more direct impact. I couldn’t help but feel that a lot of the work I was doing was writing documents and proposals that sounded good on paper but didn’t necessarily translate into action. I was longing for more direct impact, longing for the days where I was hands-on as a software developer, working closely with other engineers, building cool stuff, shipping it to production and seeing how people out there start using the things we designed and built.

In May I took 5 weeks off from work. Stack Overflow has this amazing perk where you get 4 weeks of sabbatical leave once you’ve been with the company for 5 years. Having hit my 5 years earlier in 2024, I decided to take some time off to recharge and reflect on where I want to be in my career. My sabbatical gave me time to unwind, read, work on pet projects (that’s where I built Root Loops) and reflect. We saw some early signs of summer in May which allowed me to lounge in the hammock in the backyard quite extensively - and Lenny was in for the ride, too.

My time off helped me recharge, get more clarity on where I was and what I wanted from my professional life. Taking some time to think made me realize how I had grown increasingly frustrated about my job, my lack of skin in the game and how I had become too comfortable in my position without growing as much as I’d wanted. This frustration, I realized, started bleeding into my private life more and more and I needed that to stop. It became more and more clear to me that I wanted to be more hands-on again. Strategic and foundational work is nice, and I appreciated everything I learned about running an engineering organization, but I felt that I was getting way too comfortable, staying too far away from the gnarly challenges, the tough problems. I shared my thoughts with my boss, our CTO, and we talked extensively about what we could do. I am grateful for how well my boss handled this situation. He helped me think through the options we had at Stack and together we tried to find ways to shape my role into something new that better met what I was looking for. Unfortunately, none of the options we had at the time were particularly compelling to me at that point. I sensed that it wasn’t because these weren’t interesting problems to solve, but rather that somewhere deep down I had already come to the conclusion that it was time for me to move on from Stack Overflow after 5 great years with the company (and to be candid, the previous year’s layoffs and ongoing focus on AI probably didn’t help keeping me engaged)

In July, I handed in my resignation.

Finding a new job after being a Principal Engineer was a little odd. There’s this natural notion that your career should have a steady progression. So being a “Principal Engineer” in my previous job made me look for “Principal Engineer” or comparable positions at other places. Thing is: there just aren’t many Principal-level positions out there. For a good reason, there are only so many very senior engineers you need at your company. I’m a generalist, I’m an experienced software developer and I’m equally experienced as a technical leader. So after looking for the next step up unsuccessfully for a bit, I started relaxing my criteria a bit. I started looking for engineering management positions, senior software developer positions, VP of Engineering positions, and similar. It helped me a lot to reject the idea that there’s got to be some kind of “progression”, that I have to “climb to the next level” with my next job. Jobs and companies are way too different, any sense of “progression” is made up anyways, and the work I’m doing matters so much more than the title I’ve got.

I found a new job at Gigs, a startup in the telecommunications space. It’s a fun place and a young company, and with that comes a healthy amount of chaos. Joining an earlier-stage company felt refreshing to me. There are a lot of problems to solve and I can apply a lot of my previous experience in a new context. I was anxious about starting over again and joining a new place. I knew that this meant I could be more hands on and step out of my comfort zone again, which was exactly what I was looking for after getting a little too cozy at Stack. But with every new start you risk joining a place that just isn’t the right fit for you. Luckily, Gigs turned out to be full of genuinely lovely people with an exciting amount of gnarly challenges. I joined Gigs as a Software Engineer which forced me to pick up Ruby, Rails, and Go quickly. I was thrilled to be hands-on again, to build and ship and deploy and operate and tweak and fix and observe. However, after about 8 weeks an opportunity came up to step into an Engineering Management position, leading one of our teams and slowly working myself into more cross-cutting leadership efforts. As much as I was thrilled to be back in the bits and bytes and get my hands dirty with Rails and some Go, I could sense that I’d have a bigger impact walking in engineering leadership shoes once again. So after a brief period of being hands-on again, it seems like I’m once again “post technical” and in the engineering leadership saddle, but being in a young and vibrant company this time feels a little different than it felt earlier in 2024. Let’s hope that this excitement carries over way into 2025 and beyond.

Leisure

With 5 weeks of vacation (the Stack Overflow sabbatical) at my disposal in May, I found myself in the wonderful position where I had to think about how to make the best use of my time. I planned my sabbatical carefully and wanted to make sure I don’t just spend all my time sitting in front of a computer — after all that’s what I do when I’m not on vacation, so what’s the point? I came up with a list of things I wanted to do and things I had been putting out for too long and I made sure that this list included quality time with family and friends, learning new things, finishing up some projects I wanted to finish, and doing things that would pay off in the future. Not all of these things fit into the 5 weeks of my sabbatical and kept me busy throughout the remainder of the year instead. My time outside of work has been unusually busy and productive this year. Sometimes I got to do fun things, often I got to deal with things that I had put off for too long because they suck, but I’m grateful and happy I took the time to get them done.

Gardening & Landscaping

My wife and I spent a ton of time getting our garden back in shape. We bought a house about 5 years ago, and with that house we bought a gorgeous but quite labor-intense garden surrounding our home. We spent the first few years in maintenance mode, not making too many changes and learning how nature changes throughout the seasons here. After a few years, however, we started noticing things we needed to take care of. Trees that had grown too large, shrubs that were dead or sick and had to be taken out, hedges that needed to be cut back generously, small landscaping projects we wanted to do.

Hydrangea in our garden.

We started the year cutting down an old cherry tree that had grown too large close to our garage, causing problems with the drain and foundations of the building. I hesitated to cut down that tree as it was a beautiful tree bearing fruit every summer, but we couldn’t ignore the problems it caused and would cause further down the road if we didn’t act. Cutting down this tree also cleared up some space for us to install a good amount of solar panels on our garage that helped reduce our energy bill significantly.

We spend a ton of time trimming, cutting, and removing old shrubs and plants, making space for the healthier plants in our garden to grow and thrive. While we had been hesitant doing too radical cuts in the first few years we learned the lesson that a healthy garden needs generous tending and care every now and then, and most (if not all) the plants we cut back drastically came back much better than before.

We started the biggest project of the year in August when we decided to redo an earth wall on the west side of our house. We ripped out a ton of ivy, dead shrubs, and put together five tonnes of sandstone to create a gorgeous structure supporting the wall. I’m really proud of the result and I’m sure this structure will continue to look gorgeous for decades to come.

A small section of the sandstone wall we put together in late summer.

Camping

Luckily there’s been time I did not spend with landscaping and yard work. In July I went camping with my friends. Unfortunately we got soaked badly as it was pouring most of the weekend, but we made the best of the time we got together and had a ton of fun, a bonfire, drinks, good food, and some time out in nature.

Of course it’s nicer to spend time in nature when the weather is nice but even with bad weather I genuinely love the annual camping weekend we do. It’s a great way to escape from civilization, be outside, and completely disconnect for a short time.

My Moped

I only managed to take a single ride with my moped, an 1959 (I believe, it’s hard to tell precisely) NSU Quickly I restored a few years ago, this year. The trip ended with the chain coming off, which is likely caused by the rear wheel not being in the proper position after I reassembled it last year, giving the chain too much slack. I fixed it and continued my ride with greasy fingers, but it was a great reminder that I really need to finish my moped restoration project properly soon.

The restoration of my NSU Quickly isn’t finished yet. I redid the fuel tank, the carburetor, pedals, wheels, tires, speedometer and breaks so far. The most obvious thing that’s still lacking is the frame and paint. I’ve been planning to take it to a shop and get it sandblasted and painted properly but in order to do so I’ve got to disassemble the entire thing and I’ve been putting that off for a while now since it’s just going to be so much work. Another thing on my list is to fix the clutch and maybe give the transmission a do-over. Maybe 2025 will be the year, who knows.

Doppelkopf

Of course this year also saw a healthy dose of playing Doppelkopf with my friends. We’re playing once a month at a local pub. It’s always good fun and a great way to meet my buddies, have a few beers, talk shit and have a good time.

Guess who played a Damensolo with this hand.

I’ve been getting better at Doppelkopf in recent years but so have my buddies. I keep track of every game and at the end of a year we get together and figure out who played best and scored the most points throughout a year. I haven’t evaluated 2024 just yet, but it looks like it won’t be me getting a trophy this year. Damn.

Learning

I invested some time in 2024 to learn a few new things. Besides the weird and fuzzy stuff you learn about life and being a human being, I picked up a few new tools and frameworks and got a better understanding of things I picked up before.

Some of the things I looked into in 2024 are:

• Svelte and SvelteKit. I started looking into these as they had become the new frontend tooling of choice at Stack Overflow, and I continued looking into both pieces of technology when I built Root Loops. Both seem like a really good choice when you want to build a rich and interactive frontend, and with SvelteKit you get a straightforward and easy-to-learn way to get some more structure for a single page application or something where you a simple server-side backend is good enough.
• Kubernetes. As part of Stack Overflow’s journey into the cloud (and our multi-cloud strategy) we started looking heavily into Kubernetes. I managed to avoid Kubernetes until 2024 (I worked with other container orchestrators before) and decided that it was time to close this knowledge gap. I read a book on Kubernetes and set up a k3s instance on my own infrastructure to get started. I think Kubernetes has come a long way. It’s still a beast to learn, but with hosted options and by sticking to certain abstractions it feels much more manageable than what I had seen when I first skimmed their docs a few years back.
• Ruby and Rails. I had to look into Rails and Ruby as part of my new job at Gigs, where we’re relying on Rails to build the majority of our backend business logic. Rails and Ruby have fallen out of flavor a bit in recent years so I wouldn’t have expected to ever be in a position to learn these in my career after their hype in the early naughts. Both are rather easy to pick up, especially if you know concepts like MVC and the Active Record pattern from other languages. I like how productive you can be in Rails, especially when you’re trying to get something out to production quickly. However, I sense that neither Ruby nor Rails will ever become my favourites due to their lack of static typing, mediocre tooling support (LSPs, reliance on external libraries over a solid standard library), and rather unconventional idioms that can easily turn into foot-guns.
• Go. Just like Rails and Ruby, I had to pick up Go for my new job. I had dabbled with Go before but never went too deep as it’s a language that strikes me as utterly boring and primitive (which, to be fair, seems to be part of the point of its design). Go and its ecosystem seems like a solid choice these days, with a solid standard library and a very pleasant learning curve. If only the language and idioms weren’t so horribly clunky…
• Nix and NixOS. I tried to get more familiar with Nix for a while now, but every time I tried, I got burned by the ridiculous learning curve, the vast, outdated, and scattered documentation, and the weird lack of acknowledgement of these problems within the Nix community. Lately, Nix was surrounded by a whole bunch of drama that made me reconsider whether it was really smart investing any time in learning it. However, I found a way to start small and ease into it, and I’m rather happy with my current usage of both Nix and NixOS. I started setting up Nix (using flakes) to set up developer environments for my pet projects - and thanks to this GitHub repository doing so was a breeze. After a while (and some encouragement from a colleague at Gigs) I decided to take NixOS for a spin on my personal laptop and I was surprised how easy it is to set up if you’re familiar with setting up a bare-bones Linux distribution of some sorts.

Pet Projects

In 2024 I finally managed to design, build, and ship an idea that has been sitting in the back of my mind for a few years. During my sabbatical, I spent a wild amount of time on designing and building Root Loops, a tool to generate your own terminal color schemes, and I had a blast doing so.

Building something quirky with a rather unique design was a fun experience and one of the things that made me realize how much I missed building and shipping something. I wrote a blog post to capture what I’d learned about color theory and designing terminal color schemes, and that one got somewhat popular. I spend some time here and there extending Root Loops over the course of the year, adding more and more exporters for various terminals and command line tools, and I’ll continue to add more further down the road. I built Root Loops with SvelteKit and it’s been a great choice for what’s mostly a single page application and some static content.

Root Loops gathered some traction and got picked up by a few podcasts, newsletters, and blogs, which was great to see. There have been a few active contributions to the GitHub repository and I’m eager to see what else is coming in the future.

Besides Root Loops, I built a silly Air Horn app for funsies (see also this blog post).

Last year, I rebuilt this very website (hamvocke.com, that is) and wanted to write a bit more than before. With 8 blog posts (including this one) and a few updates to my /now page published in 2024, some of them silly and mundane, some profound, some very personal, I like to think that was a success.

Health & Exercise

2024 was a good year for exercising and overall health. In January, two of my friends and I signed up for a local 5k race. I’m not much of a runner but I know I’m capable of running 5k without a lot of trouble. Unlike my friends, however, I’m not really fast. We turned this into a small competition which motivated me to actually set aside some time early this year to train for the 5k race, work on my cardio, endurance, and speed. During my (fairly infrequent) training sessions I managed to finish my 5k in about 25 minutes (most often I took Lenny with me on my runs which messes with the time a little as he needs occasional breaks to sniff and pee — but honestly, I didn’t mind the breaks either). I finished the actual race in 24:04, a pace I’m really happy with.

Most of my exercise revolves around powerlifting style training. I’m fortunate to have a well equipped home gym that allows me to train pretty much whenever I can find the time. I focused on building out my strength over the last few years. The longer I’m doing this and the older I get, the harder it becomes to increase my peak strength, and I got somewhat tired of grinding out heavy sets of the same exercises (Squats, Bench Press, Deadlifts, Overhead Press) over and over again. I decided to switch things up a bit in 2024. First, I wanted to cut my weight back a little more without losing much of my strength. Second, I wanted to try new things that are still strength-related but outside of classic powerlifting. Over summer, I ran Brian Alsruhe’s “Every Day Carry” program. It’s a program that borrows concepts from powerlifting and strongman sports, incorporates daily heavy carries using sandbags and farmer’s walks implement, and kicks your butt with a ton of giant sets that leave you gasping for air. I had a ton of fun playing around with new exercises and enjoyed the carrying part much more than I expected. The giant sets and strict timing of the program massively helped me improve my conditioning. My top strength didn’t change much (if at all) over the course of the year but I can tell how I’m coming out of 2024 with much better conditioning and a better base strength, making me feel more secure and confident at sub-max attempts of my main lifts. I’m considering running Every Day Carry again in 2025.

Overall, I worked out on 231 days in 2024, which is the highest amount of workouts I’ve ever tracked in a given year. I mostly train in my garage gym and my backyard (for carries, sandbag sessions and farmer’s walks) - but this year I finally managed to set foot into a real gym for the first time in years. When I visited Gigs’ office in Berlin in late fall, a coworker took me to Berlin Strength and I had a ton of fun (ha!) lifting with some like-minded people around me.

Deadlifting in chicken socks at Berlin Strength

In 2024 I kept my bodyweight in check and managed to cut back a little bit. I’m considering gaining some weight deliberately next year to see if that helps me with improving my top strength and build some more muscle, but as someone who used to be obese earlier in his life this is a decision that doesn’t come easily.

This year I planned to be more mindful around my alcohol consumption. I like having a few beers in a social setting but I’m not one to ever drink alone or outside of a social gathering. Looking back at 2024, I think I managed to do better than in 2023 by being better at moderation, having fewer drinks in social settings, and abstaining from drinking for weeks on end multiple times this year.

Travel

I left the country twice this year. My family and I traveled to Athens, Greece in March and had a great time visiting old sites and immersing ourselves in history for a few days.

In October, I went to Portugal with my new company. As a remote-friendly company, we get together in person twice a year, and Portugal was my first chance to meet everyone in person. We had a great time socializing, strategizing, getting everyone aligned, and checking out the impressive waves of Nazaré. It’s a privilege to be able to see such beautiful corners of the world as part of my work and I’m grateful I got a chance to visit Portugal this year.

Apart from these two trips, I went to Berlin twice this year to meet some of my new coworkers. I tried to go three times in total, but the first time ended with me crashing my car in a gnarly accident that shook me up for quite a while. Luckily nobody got harmed in the accident and my insurance company helped me take care of the damage.

Music

There’s one musical highlight that stands out for me in 2024 without any doubt. It’s Bilmuri.

I discovered this weird, eclectic, and ridiculously catchy mix of country, pop and metalcore breakdowns in early 2024 and couldn’t get enough of it for the remainder of the year.

Other highlights of 2024 include:

• Sum 41’s farewell album “Heaven :x: Hell”. Sum 41 have been a personal favourite since I heard their first LP as a teenager, and they ended their career on a high note. I really enjoyed their last album and appreciate the thorough mix of throwbacks to their pop-punk days as well as their heavier, more metal-influenced stuff.
• Bring me the Horizon’s “POST HUMAN: NeX GEn”. Lots of bangers on this one put the entire album on hot rotation for me. It made me appreciate the creativity and ever-changing style of Bring me the Horizon so much more than ever before. I largely ignored BmtH until very recently and took the plunge to take their entire discography for a spin in 2024, and I realized I should’ve paid attention to them much earlier.
• Amyl and the Sniffers popped up on my radar with their “Cartoon Darkness” release this year. I spent some time listening to all their stuff and found some really fun stuff in there. Australia’s punk scene doesn’t disappoint.
• More shout outs go to Tiny Moving Parts, Jack Kays, Driveways and Four Year Strong who all dropped new LPs throughout the year that I really enjoyed.

Books

If I tracked everything correctly, I read and finished 12 books in 2024. This year I had quite a few very mediocre and underwhelming ones - I don’t know if this is me getting more critical or just bad luck.

Here’s what I read, in rough chronological order.

• The Manager’s Path by Camille Fournier. I started this book a few years ago but only ever read a few chapters that had been relevant at the time. This year, I finished it cover to cover. It’s a great book full of helpful, inspiring and reassuring advice for folks in leadership positions in the software industry. If you’re a senior engineer with aspirations to be a mentor, tech lead, or considering to grow into management ranks, I recommend you check this one out.
• Microservices: Up and Running by Irakli Nadareishvili, Ronnie Mitra. It was becoming apparent that microservices would become more and more of a thing at Stack Overflow. I worked on microservice architectures before but that’s been years ago. I was looking for some inspiration on kickstarting a healthy microservices journey and see if recent literature had a few helpful pointers that I wasn’t aware of. Unfortunately, this particular book really wasn’t giving me what I was looking for. It’s an authoritative “do this, then that” style of book (which I think is the point of the “Up and Running” series at O’Reilly) but I find that kind of attitude incredibly hard to accept in an area that’s as full of trade-offs as software architecture.
• Leviathan Wakes (The Expanse) by James S.A. Corey. Finally some fiction! “Leviathan Wakes” is hard Sci-Fi. Space ships, foreign worlds, interplanetary travel, politics, factions and plotting. It was captivating and mysterious and the start of the long “The Expanse” series. I couldn’t get myself to continue the series yet, but I might pick up more of it in the future.
• The Software Developer’s Career Handbook by Michael Lopp. Short and enjoyable tales and anecdotes on what it takes to be a software developer. Lopp’s a great storyteller and his books are structured in short chapters, making them an enjoyable and quick read on the go. During a time where I was having a bit of an identity crisis at work, this book might have sparked a few ideas and helped me figure out what I want for myself.
• Kill it with Fire - Manage Aging Computer Systems by Marianne Bellotti. Another book to serve as inspiration, this time for handling our aging system at Stack Overflow. After finishing this book I realized I didn’t really take away anything new. For me personally there was not much to get from this book. It’s not overly technical and talks quite a bit about how important it is to consider the social aspect of introducing change and replacing aging systems. It’s probably not a bad book per se but it left me too uninspired - most likely since I’ve been through most of the difficulties of driving larger-scale change and the human challenges that come with that during my time as a consultant a few times.
• Dune and Dune Messiah by Frank Herbert. I watched the Denis Villeneuve movies and decided to check out the books. Reading “Dune” made me appreciate the movie adaptation so much more as it’s fascinating to see how well Villeneuve managed to bring even difficult settings to the screen. The books themselves are good, they’re classics for a reason. The world-building is top notch and the story is captivating. Unfortunately, I found Herbert’s narrative style to be very exhausting and hard to enjoy. The characters would often come across as too high-and-mighty for me and the philosophical undertones got old very quickly. As much as I enjoyed the plot overall, I couldn’t get myself to go beyond the first two books of Herbert’s Dune legacy.
• The Art of Leadership by Michael Lopp. Another one by Rands, once more short tales, this time around leadership. Similarly to “The Software Developer’s Career Handbook” I took quite some inspiration from it and otherwise enjoyed the light-hearted anecdotes.
• Agile Web Development with Rails 7 by Sam Ruby, Dave Thomas. I had to pick up Ruby and Rails quickly for my new job at Gigs, and I tend to learn best by reading books. I picked up this one as it seems to be fairly standard. It’s solid. It covers a lot of ground and walks you through building a Rails-based e-commerce application end to end. Not too exciting, but it definitely got the job done for me.
• The Library at Mount Char by Scott Hawkins. Finally more fiction! “The Library at Mount Char” is a dark and unusual fantasy story that kept me on my toes. I didn’t expect to enjoy this one as much as I did.
• Dark Matter by Blake Crouch. I had read “Recursion” by Blake Crouch a few years ago and found it to be fairly “meh”. “Dark Matter” hit differently though. It’s a mysterious story that kept me turning pages way past my usual bedtime. If you’re cool with thrillers and don’t mind a healthy dose of science fiction, this one’s a good one.
• A Philosophy of Software Design by John Ousterhout. I had this on my radar for years but never picked it up. When I joined Gigs I saw that there was an ongoing book club discussing this book and I joined. It’s solid. Much more level-headed advice than the often-cited (and recently often rejected) “Clean Code” by Uncle Bob.
• Platform Engineering by Camille Fournier. Okay, this one I actually didn’t finish just yet, but I still wanted to include it here. Camille Fournier shares her experience in establishing and running “Platform Engineering” teams. I’ve had my gripes with the way we split our teams between “Product Engineering” and “Platform Engineering” at Stack Overflow, and found myself researching if and how the ideas of “Platform Engineering” teams could help us at my new job at Gigs. After really liking Fournier’s “The Manager’s Path” a lot, I decided to check out her latest book and so far I’m not disappointed.

Cooking

I enjoy cooking, and I did a few noteworthy cooks in 2024.

Overall, I continued diving into the world of home-made pizza. I made a few nice Neapolitan-style pizzas that turned out to be my best ones so far. I’m slowly getting better at creating evenly round shapes, getting the char on point (I still burn them sometimes for sure) and making the dough rise to a nice crisp and airy goodness.

A classic Neapolitan-style pizza with prosciutto and some balsamic vinegar.

A pistachio cream base with mortadella (and some burrata I added after taking this picture).

Mozzarella, burrata, pickled red onions.

My wife gifted me “Perfect Pan Pizza” by Peter Reinhart for my birthday in March, and that book inspired us to experiment quite a bit with Dertroit-style pan pizza and Focaccia. Focaccia has become a staple for barbecues and get-togethers with friends and neighbors that I really enjoyed preparing and bringing for larger crowds of people.

Focaccia with mortadella, pistachio cream and burrata (can you tell that this combination has become a recurring theme?)

Outside of Pizza, I fired up the old smoker a few times this year. We had friends over for some nice Pastrami using beef brisket. We served it on home-made sandwiches and some rye bread we got from a local bakery, together with pickled gherkins and mustard. I also smoked some trout and pulled pork this year, but didn’t take good pictures.

Pastrami on my smoker, Lenny in the background

And lastly, following my yearly tradition I started curing ham earlier this week, that’s going to be ready for cold-smoking in about 3 weeks. I chose lean cuts this time to switch things up from last years rather fatty hams. My 2023/2024 batch turned out great and a lot of my friends enjoyed their share. I hope this year’s batch will be equally well received.

Some of my 2023/2024 ham

Here’s to a great 2025!

Once more I’m grateful that I can look back at a year full of positive change, health, and time spent with loved ones.

I know that things often seem grim and it’s easy to lose any sense of optimism if you follow the news. Don’t let the doom and gloom of our daily lives take away from the beauty, kindness, and opportunities you can find out there every day. I hope you all have an amazing year 2025 and get a chance to enjoy many great moments, health, fun, and time spent with the people you love.

Stay awesome and take care!