Hi! My name is Herbert and I’m a software engineer at SumUp. We’re a multi-language company, so we use a lot of languages in our ecosystem. These include Golang, Ruby, Elixir, Erlang, Javascript (Node, React), Swift, Kotlin, and Java.

My team worked extensively with Ruby for over a year. When the time came for us to create a new microservice, we had to decide whether to stick with Ruby or change to a new language. Even with all the existing languages in our ecosystem, we decided to try something new, because we spotted an opportunity to solve problems and grow our customer base.

Here are the main reasons why we ultimately chose Golang.

1 — Engineers want to use it

SumUp is a fast-growing company, and we’re always on the lookout for new engineers. As such, we needed to choose a language that people want to use.

Go was among the most wanted languages in 2019's Stack Overflow Survey, so we were confident that potential new team members would like to work with it. It’s also very simple to onboard engineers and get them productive early with Go.

2 — It’s easy to learn

Go is one of the easiest languages to learn, with only 25 keywords. The docs are good, and there’s plenty of great material like A tour of Go, which flattens the learning curve even further.

Our developers had a lot of experience with the Object-Oriented Paradigm. If we’d chosen Elixir, for example, a change to functional programming would make the learning curve steep for the team.

Go is very explicit, making it clearer and easier to understand. There are no unnecessary complexities.

Our team was so enthusiastic about learning Go that we hosted a Go Meetup in São Paulo, to talk about our initial experiences.

3 — It’s a compiled, statically-typed language.

I’ll tell you a secret if you don’t currently work with a typed language: You’ll either love it or hate it.

If you initially hate it, rest assured that you’ll eventually begin to see the benefits.

At the end of the day, software’s biggest cost lies in maintenance rather than the time it takes to create the code. Typed languages make it much easier for you to understand how the software is working. And statically-typed languages help you identify errors early on in the development process.

Static typing usually results in compiled code that executes quickly. The compiler knows the exact data types that are in use, so it can produce optimized machine code.

4 — Go’s tooling is helpful and opinionated

If you install Go, you’ll have already lint, format, and test tools.

Use gofmt or goimports in your code, and you'll instantly have all the settings and best practices adopted by the community. You can go a little further with more restrictive rules. I did this for a few projects and learned even more about the language. Go is very opinionated by default with its code style. By following what is already defined, you can avoid wasting time arguing with your team about small details.

Go also comes with a test framework, so you have all the basics to create good and maintainable software without having to worry too much or choose frameworks.

5 — We wanted a common language within our tribe

At SumUp, we work with the concept of squads and tribes, as per the Spotify Tribe Engineering Model. My squad was part of a tribe that uses many programming languages. We wanted to have a common language that all our squads could use, so that any engineer can switch between squads and deliver value quickly. I realise that this goes a little bit against the principles of a multi-language company, but we saw real benefits in using Go as our main language.

This is good for the company, but also for developers who want to change their current context, or maybe even live in another country. Our tribe has squads in two locations, Berlin and São Paulo. If someone wants to move and continue working in the tribe, they won’t have technological issues. Last year, one of our software engineers enjoyed life at SumUp across two continents.

6 — No Silver Bullet

Go will never be our silver bullet and we don’t expect this from any single language. As a rule, you shouldn’t expect this from any particular technology.

Go proved to be a good solution for our specific needs this time, but this doesn’t mean that it will be the solution for everything.

And we’re perfectly happy with this. We need to also have space to create new things and find the right tools for the job.

Bonus reason — Amazing mascot, great package names.

Did you see their mascot? You can even create your own gopher! Go also has incredible library names like Gin Gonic, Gorilla, and Buffalo.

—

Are you using or planning to use Go in your company?

How is your experience with Go? Are you enjoying working with or learning this language? Send me a tweet at @herberth3nrique.

I hope you liked the reasons I shared with you. I chose to focus on benefits that the language brought to my team, so I haven’t even mentioned the most common benefits of the language, such as concurrency, performance and garbage collection.

If you enjoyed this article, don’t forget to share it on Twitter!

If you understand Portuguese, we have a podcast about how we deal with hardware, multi-languages, and microservices at SumUp.

Take a look at our opportunities in Brazil and join us.

Follow us on LinkedIn and on Instagram.

6 Reasons why my team decided to use Golang was originally published in Inside SumUp on Medium, where people are continuing the conversation by highlighting and responding to this story.

You can read the original post here on my personal website :)

I had been working with software development for more than ten years, but only in the last four years of my career I realized I can call my self a “frontend”.

Okay, from the beginning: My first job was working as an intern on a really small company with a back-office system made in ASP. yeah, not everyone starts your career in a cool startup with fresh new code 🤷‍♂️ After this experience I think I’ve developed few traumas with frontend development, if you need to create a few hacks to work on IE6, we only talk about javascript to validate forms and that table madness… life wasn’t so good for frontend on those years (and this doesn’t even exist… web master maybe?)

Let’s fast forward a little bit. Around 2011 I started to work in a digital agency and there I was only focused on backend. Well, only until I learned that solving the problem is more important than technology and that an old friend taught me that javascript could be fun and everything changed in my life (thank you (gilini)[https://twitter.com/the_spkr], you had no idea how you changed my life). I was still mostly working with backend, but javascript was becoming my biggest love in the next years.

That part is super cute, but I need to admit it… I was that jerk who hated CSS. Do you know why I hated it? it’s because I didn’t understand how to use it (Actually it’s the same reason some backend developers hate it). So, it takes time but I could evolve and learn it and see I was a jerk the whole time :)

Fast forward again and today I work with a lot of backend languages, take care of frontend engineers, and don’t mind working with golang, CSS, rust, or react.

I don’t care about naming, I say that I’m a software engineer because it’s easy. I don’t care to be named backend, full-stack, or frontend. And you now asked me what I learned from this?

Solving the problem is more important than technology

I learned javascript to help in a project. I see people today at Sumup trying to learn frontend or backend to help their teams and achieve great things

If you’re hired as a software engineer is to solve problems and not care what technology, language, or whatever.

The frontend evolves super fast and this is amazing

When I started my career frontend was a lot of tables and today we have amazing things. Javascript is a language with really great features that are evolving every day.

do you remember about that “javascript fatigue” a few time ago? Let me told you that all these new things being created all the time is one of the most fascinating things in the frontend community. You don’t need to learn everything, but see all these things and learning new things is a privilege of our time.

Do what you love and have an open mind

Or maybe: don’t be a jerk.

That’s the basic but sometimes a few people don’t realize that. If you’re a backend, it doesn’t mean you’re better than someone just because of your language or whatever.

Have an open mind, try new things and maybe you’ll find a new love :)

Did you find this post useful?

Click here to share this post on Twitter and tell me what you think or just send me a message at @herberth3nrique. :)