Unknown's avatar

About Anthony Mattson

If you want to know more, read my About section.

2025: A Year of Change and Renewal

2025 has been a powerful reminder that change is the only constant in life (thanks, Heraclitus). Despite my best intentions to focus on advancing my career, depression, anxiety, and an overly demanding job had other plans — draining my energy and stealing my focus. On top of that, there was the looming uncertainty of when my employer would finally enforce a return-to-office policy, one that would require me to move to a significantly more expensive state without any increase in pay.

Fast forward to a month ago: everything shifted. I was faced with a decision — accept a severance package and leave, or continue pushing my stress levels to hold onto a job that felt like it was already on borrowed time. Needless to say, I chose the severance. It turned out to be one of the best decisions I’ve ever made, allowing me to walk away from a mountain of stress.

With unemployment on the horizon, I dove into the process of filing for benefits and began applying for new roles. Luckily, one of the local companies I had applied to before the severance reached out for an interview. I’m thrilled to share that this interview quickly led to a new position as a dedicated Solutions Architect.

Now in week three of my new role, I’m absolutely loving it! Things have been relatively calm so far, but I fully expect the pace to pick up — and I’m ready for it. I’m finally working on projects where I can see real progress and play a direct role in shaping outcomes. There’s also a ton of new material to learn, which I’m genuinely excited about. Most importantly, I no longer have to constantly micromanage my time.

On top of all that, I recently renewed my AWS Certified Solutions Architect Associate certification and have started working toward my AWS Certified AI Practitioner credential. While I stay cautious about AI integration and the way GenAI is being handled, I can clearly see its potential. It’s time to dive in and learn everything I can.

2025, New Year, New Plans

It’s been a while. Not something I’m particularly happy about, but life doesn’t always go as planned. Our minds also have an amazing ability to complicate our lives, both intentionally and unintentionally. Over the past couple years, I’ve been working on a lot of self-discovery and self-reflections to better understand myself.

With some much needed therapy, I’ve come to better understand how my mind works. Therapy has helped explain why I keep producing all these plans about what I want to do. I start them all but never finish them. Confirmed it isn’t ADHD, but I’ve had complications in my life that have effected my executive functions. TLDR, I love to start new things and overwhelm myself to the point I’m not capable of focusing on anything. Now that I’m working on myself, it’s time to start rethinking my approaches to my own personal development.

So yeah, I have a lot of projects I’d love to work on. I need to start limiting myself and focus on fewer projects/tasks at a time. Seems obvious, but that’s now how my brain wanted to work all this time. With that, I’m going to focus on one professional and one personal goal.

My current professional goal, finally get an AWS Certified Solutions Architect Professional certificate. Going to focus on fine tuning my skills to be an AWS Solutions Architect.

My current personal goal, learn Godot and finally start making some video games as a hobby.

Additionally, I will document hurdles I come across while working on these tasks. For example, I will document learning how to setup SSH with GitHub. There is no end of online guides, and I always find myself needing to reference several guides. They all seem to miss something important. Dual intention with this, record the steps for my future reference and share them for other in case it helps. This will be a continuing goal, so it will be a long term goal.

With that, time to get started!

Never Just Copy Code

When I’m learning something new that involves coding, I’m always grateful when working code examples are provided. Whether I’m working on training modules, looking up how to accomplish a specific task, or troubleshooting code. While I try to learn what I can from reading, I’m much more of a hands-on person and learn best getting my hands dirty, so to speak.

However, I very much understand there are pitfalls for using these code examples. Namely, it is very easy to simply just copy/paste the code and that’s it. If it works, all good. But do you actually know what the code does? If it breaks or doesn’t perform as expected, can you troubleshoot it? If you wanted to alter it to behaving differently, can you? This is why I press on myself to never just copy code.

Whenever I copy code, I make a habit of breaking it down. I make sure I understand every part of the code, what the code does, and how it does it. I want to make sure I know what I’m doing and learning from the code example so I can further improve my own knowledge.

For example, I’ve never worked with asynchronous programming prior to writing my project Discord bot. I was fortunate that the Discord .NET community has really great documentation on how to get started. with all the necessary code. When I was following the documentation and using their code, I made sure to break down each line to make sure I knew what I was writing. This even lead me down a rabbit hole of reading the Microsoft documentation for understand what asynchronous programming is.

I’ll be honest, I’d have no idea how to troubleshoot my bot if I ran into any issues. Not going to say I’m an expert, but I definitely learned a lot about asynchronous coding.

It’s always good to keep learning.

Getting Started with Containers

For a while now, I’ve been wanting to know and learn more about containers. Nothing like a new job that specializes in containers to jump start that process.

If anyone is wondering where a good starting point is for learning what containers are, might I recommend the Docker tutorial container getting-started.

$ docker run -d -p 80:80 docker/getting-started

This is a simple image that includes a tutorial website that takes you through the basics of using Docker. Goes through how to pull an image, build an image with code, update an image, and deploy all with using the CLI. Doesn’t really get into orchestration but does bring it up near the end. However, an added benefit in my book, it’s a fully functioning image that includes a multi-page website. Perfect for running quick container tests.

It may not be what you intend to do with a container, but it is very nice baseline. So much so, I’ve started using it to play around with the container services in AWS. Started off by deploying a copy of it to an ECR repo. From there, I’ve used it to test out different scenarios in ECS and EKS. Testing out EC2 vs Fargate instance types; testing out multiple deployments behind a load balancer; and testing a multi-container task. Perfect for helping me know I’m deploying my containers correctly and they work. I know I can build my own container and test it locally, but I haven’t gotten to that point yet.

I do have a couple of my own ideas to try testing out as well. Just need to build the images. Current plans include my Discord bot, a V Rising game server, and some of my own website builds. The bot will be interesting as I haven’t yet tested .NET Core in Linux and want to give that a try. The V Rising server is Windows only, so that will be nice experience with a Windows container. The websites will likely be Blazor/.NET Core, so Windows is a given; but Linux is an unknown. Similar to my Discord bot currently. Either way, I’ll be learning along the way.