Rather than spending a month reading a book before I start using something, I need to get into it as fast as possible. And that’s where my Kotlin journey began. So instead, we went with TeamCity, which had support for writing pipeline-as-code in Kotlin. We tried using CircleCI, a cloud-based AI platform, but we had to abandon it because it didn’t fit the job. I went from knowing nothing about Java to having a fully working piece of code after just a few days - and winning the challenge!Īround this time, we had a requirement to store our pipelines as code. My first experience with that language came as part of a challenge with the automation team. At this point, I was working mostly in PowerShell. So instead of focusing on code, I started developing our build framework, making it better suited to our team’s needs. The company had 14 teams spread across the globe, and every developer had their own way of approaching how to code and build stuff. I became responsible not just for making the right decisions, but also for how things looked on the back end.Īround this time, I started thinking about not just what we were building, but how we were building it. I then touched on C# when studying for my Master’s, getting a job the summer I left university as a C# developer, where I worked on automation and developed a framework for testing in C#.Īfter some time, I got an offer to switch to product engineering, to be someone who develops code that goes to production, which was super exciting. I used Pascal to write my first code, before settling on C for a while. I started coding when I was in third grade. In this article, I’ll explain what drove me to take on that challenge, the benefits of working in Kotlin, and why Productboard is the perfect fit for Kotlin engineers. A look at engineering inside ProductboardĪ couple of years ago, I decided to learn a brand-new programming language: Kotlin.

Java and kotlin