Optional Dependencies
Sometimes a library you are writing may have optional dependencies. E.g. “if apache http client is on the classpath, use it; otherwise – fallback to HttpURLConnection”. Why would you doContinue reading
AWS “Noisiness”
You may be familiar with the “noisy neighbour” problem with virtualization – someone else’s instances on the same physical machine “steals” CPU from your instance. I won’t be giving cluesContinue reading
Log Collection With Graylog on AWS
Log collection is essential to properly analyzing issues in production. An interface to search and be notified about exceptions on all your servers is a must. Well, if you haveContinue reading
The Precious Feature Design Meetings
As we know, meetings is where work goes to die. Discussion about the point of meetings aside, there is one type of meetings that I love. It has many names,Continue reading
KISS With Essential Complexity
Accidental complexity, in a broader sense, is the complexity that developers add to their code and that is not necessary for the code to work. That may include overengineering, overuseContinue reading
Getting Notified About RabbitMQ Cluster Partitioning
If you are running RabbitMQ in a cluster, it is not unlikely that the cluster gets partitioned (part of the cluster losing connection to the rest). The basic commands toContinue reading
A Non-Blocking Benchmark
A couple of weeks ago I asked the question “Why non-blocking?”. And I didn’t reach a definitive answer, although it seemed that writing non-blocking code is not the better optionContinue reading
Why Non-Blocking?
I’ve been writing non-blocking, asynchronous code for the past year. Learning how it works and how to write it is not hard. Where are the benefits coming from is whatContinue reading
Time Zone Use Cases
Time zones are a tricky thing. Jon Skeet gives a pretty good overview of the horrors (at 20:10). But besides the inherent complexity of having timezones and DSTs in theContinue reading
My Most Frequent Code Review Comment
The title implies one prerequisite – you must have code reviews for every piece of code written. For that, FogCreek recently published a list of best practices for code reviews.Continue reading