I’ll keep this short. In the past 6 or so years in Amazon I’ve been mostly working with Java and sometimes a little bit of Python. There’s nothing wrong with that. I’m not against any of these languages, I might even enjoy working with them – at least when people don’t abuse design patterns just for the sake of it and use 75 levels of indirection because “best practices”, ending up with code that is impossible to maintain. And unlike what some think, I believe both languages are going to be around for a long time – their market share is far too big and they are far too widespread to be disappearing any time soon.
But I’m digressing and I said I was going to keep this short.
Like many other developers I like to spend time researching new technologies, look at new programming languages, and just experiment with things in my free time. Over the years two languages caught my attention, and I figured this is as good a time as any to start picking up on a couple of them. I’m talking about Go and Rust.
Now, to be honest: I hate new years resolution, and I don’t believe they make much sense. It’s something you commit to and then just drop a few weeks later… (fun fact: I do have some sort of yearly cycle analysis that I do regularly – e.g. around finances – but I use my birthday as a “fiscal year” of sorts). I do want to learn these two new (to me) languages though, and I figured I’d try to use this blog as an “accountability buddy”. So here we go.
I’ll be posting my notes and progress while I try to learn Go and Rust, in a format that can be used by others to learn as I go. If it ends up being decent enough it might even become a little course in Go and Rust programming. And I will release anything I end up building while learning as open source on my GitHub profile.
So there it is. Stay tuned and follow along 🙂