So I’ve been at Canonical for 6 months now, and after six months into my first full-time remote gig, and while I knew it was going to be different than office work, you never really know how it’s going to play out. Needless to say, there are some lessons I expected, and some that were new, and it’s worth examining them. Continue reading
It’s been about half a year since I wrote my last post, and I wanted to reflect back on some of the goals I had set for myself. In a nutshell, I wanted to 1) Grow HSV tech community, 2) learn some cloud technologies, 3) build something, and 4) read more theoretical books.
So halfway through the year, I feel like the HSV tech community has been growing, and HSV.py is still going strong. I still have a surprise coming, so stay tuned. But what has derailed most of my other goals is that in April, I started a new job: Software Engineer at Canonical!
I’m working on the CPC team which focuses on public and private cloud deployments. I mostly do Python library work and Jenkins pipelines to transform Ubuntu images to their suitable cloud images. It’s been great, because 1) I can work in Python and 2) I am getting to learn about a lot of cloud technologies along the way.
But, this is only my third ever job. The first time I moved jobs, I had 3 years of experience; now I have 12. I feel like there is a lot of advice out there for when you are new and swapping jobs, but not so much when you’re a senior engineer. Here are some tips I’ve discovered in the three months of working there.