I remember a job interview that I had in my early days as a software engineer. I was asked what is the Object-Oriented Programming (OOP). I tried to remember things I learned at a University and murmured something about encapsulation, inheritance, and polymorpshism.
In-memory data stores like Redis are becoming increasingly important components of modern distributed systems. Managed solutions like AWS ElastiCache are the cornerstones of the Cloud Computing.
Did you ever have troubles sleeping the night before important job interview? Have you ever felt your heart racing and palms sweating during an interview? If so, you are not alone.
Redis is one of the most beloved data stores according to StackOverflow survey. Amazon Web Services offers managed Redis as ElastiCache. It has many features that allow us to build great systems; one of them is replication.
Today I want to explore somewhat overlooked topic of code commentaries. It seems like a simple topic, yet it is the one that sometimes invokes the hottest water cooler arguments!
In my previous article I talked about why it is a good idea to write unit tests. Now I want to talk about a different question - how much unit tests to write?
In this article I want to talk about unit testing. Why do we write them? What do we expect from them?
I have heard many different opinions, sometimes quite opposite.
