Zabed Akbar's Blog

Blogs I have recently read which are worth bookmarking for future reference. Dropbox sync engine rewrite How Query Optimizer works ? Encodings Grep Commands Erasure Coding  - Save storage space and increase fault tolerance. How Netflix Uses Kinesis Streams to Monitor Applications and Analyze Billions of Traffic Flows jsoup - JAVA HTML Parser Logging with Python  - A great blog from DataDog regarding best practices for logging with Python. Lambda with CloudWatch Logs Insights - Leverage Log Insights to deep dive on logs using a SQL like syntax. Primitive Data Types C# Vs Java

Code review is a great learning and knowledge sharing tool not only for the new members of the team but for the long time company veterans as well. Having a code review process in place dramatically improves the code quality and helps detect bugs in an early stage. Much of what I wanted to write here has already been captured in this great post form smartbear. Another great blog on sa However, here are the important bits:   Author: Keep the CR small.  For bigger change, break down the review in meaningful chunks. Add TODO comments for future CR. Keep you changes under feature flag or in a separate feature branch to facilitate smaller incremental changes which are not ready to be released in production. Check this engineering blog from google on small CL . Provide a detailed context of the change. I prefer documenting context in commit message and will recommend to follow similar format from Linux project [ link ] Provide details of tests performed to verif