From one point, he’s just one of the 7 billionth people on Earth. From another point, you can see something special in him. You can see a true passion for software quality and engineering, genuine interest in new tools and practices, free mind and beating heart.
I’m a System Engineer with knowledge in these areas:
- mostly Java and Go, but also with a little bit of Groovy, Scala and Python experience
- Gopher since 2015
- AWS user since 2010
- passionate about Continuous Integration, Continuous Delivery, and other engineering practices
- strong believer in DevOps approach, trying to make work easy for my team with different tools, scripts, and hacks
Open source:
- Contribution to several open source projects, including Open AWS Guide, protoactor-go, autospotting, flatdata and others
- One of my repositories was mentioned in AWS blog post
Recent talks:
- Selenium Camp in March 2018 with talk about using AWS for different types of testing activities
- Heisenbug in May 2018 with talk about building CI from scratch
- DevDays Vilnius in May 2018 with talk about Go implementation for Flatdata
Interested? Then don’t hesitate to contact me.
My previous post about creators of Go ended with a phrase Does it mean that they were right again? I don’t know, we will see…. And now we can say for sure that they won. They were right again. If you didn’t hear it, then you should read this post. It’s about an incident from Cloudflare regarding significant vulnerability discovered in their service. But they didn’t mention the most important part, about how it was found.
I named this post after a very well-known slogan from Apple advertising. But we will not talk about Apple, we will talk about Go, the programming language that was created by exactly that type of people. The landscape of programming languages is huge. But there is something common for almost all of them. They all trying to put a lot of new features with every release. Sometimes, they broke compatibility between different versions, like Scala did or broke their community into 2 parts, like Python.
In previous post I tried to describe why I started to look into Go. Today I want to share a small example of Go power. Some time ago we had a tiny Python script for monitoring purposes that runs into CI. Setup was simple: - download script from Git repo - download and run Docker container with Python environment - run monitoring script. The whole execution time in CI was around 10 seconds.
I looked at Go in early 2015. Of course, I heard about this language earlier, but at those moments he wasn’t very interesting for me. Things changed after I joined Russian-speaking Go community in Slack (golang-ru.slack.com). I found very interesting and skilled people there. And this was the main point that forced me to look at the language. I went on golang.org and read the documentation. After that, I tried to write a small CLI tool, which used for authentication via HTTP on some internal service.
It finally happened!
After several attempts, I finally moved from Jekyll to Hugo.
I’m also moved from Github Pages back to Amazon S3. If you’re looking for a guide, try this one. It mentioned some things that weren’t clear in the process.
You can find my CV here