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 Software Engineer with knowledge in these areas:
Go, but also with a little bit of
AWS user since 2010
- strong believer in
DevOps approach, trying to make work easy for my team with different tools, scripts, and hacks
- 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
- Selenium Camp with talk about using
AWS for different types of testing activities
- Heisenbug and DevOpsConf Russia with a talk about
building CI for a complex mobile product
- DevDays Vilnius with talk about
Go implementation for Flatdata
- DelEx with talk about
usage of AWS Lambda for infrastructure tasks
You can find my CV here.
Don’t hesitate to contact me if you have any questions.
AWS is the biggest public cloud out there. You could do almost everything with it except for running x86 Android emulator. Things were like that in the past. It all changed on May 17 when bare metal instances became GA. New instances type allows access to the underlying hardware which means running x86 Android emulators on AWS is now possible. Now you can scale your Android tests until exceeding limits on i3.
There a lot of different services, offering automated testing on real mobile devices and/or emulators in the cloud. In this post, we will not talk about how to choose one of these services. If you are interested in choosing a service which fits you, then you can start from this article. Instead, we will talk about some issues and workarounds what you may face using AWS Device Farm. In general, such issues may be split into two categories: project specific and common ones.
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.