Writing a software usually happens on a machine with a prepared testing set of data. When you write another feature, you just slightly modify the testing set. Then you just go along by modification of the existing set again and again. Does it sound familiar?
Do you often have three meetings scheduled one after each other? How do you deal with it? I find such scheduling ineffective and exhausting. It’s a struggle to keep refreshed and open minded when you run from one meeting to another.
I genuinely believe every human being has creative and innovative potential. It’s part of human code and we experience it in every day life, no matter if it is cooking, art, or engineering. Software engineering to me is a discipline on the triangle of engineering, creativity, and craftsmanship.
I uninstalled Java 8 last weekend from my computer and tried to live without it. I made couple of observations since then and needed to reinstall Java 8.
Java 11 (https://openjdk.java.net/projects/jdk/11/) was released on 25 September 2018, so I’ve decided I’ll upgrade my legacy Java web application that was written at times of Java 6. Even two month after the release, surprisingly, the tooling is not mature enough.
In this blog post I’d like to cover a few thoughts on how to build and architect resilient services in cloud. Many things are good practice for normal architecture too but some of them are cloud-specific. I should point out that this is solely my opinion.
At the end of the last year I decided to make a significant change in my career. I joined cloud-native internet company Skyscanner and relocated from Prague to Edinburgh. It’s almost three months now so I think it’s a good time to capture my experience.