I have been sharing book titles with my colleagues for over a year now – to help them increase productivity, building up habits, defining goals, etc. Unfortunately, I found a common pattern which is very ineffective – reading as fast as possible. Most of us tend to complete a book as if they were reading a story, or they are supposed to finish it. Here are some facts that we need to remember when reading these kinds of books:
Let’s say we want to add a full-text search engine to you application. Apache solr is a open source and popular choice for search engines. Now, I am going to share a simple architecture to synchronize data between the primary data-store (like mysql, mongodb, etc) and solr engine.
I am going to start writing a new series on “white hacks” that I frequently make as makeshift solutions to exigent problems. Many a times these solutions are not ideally the best approach to solve problems, but they are highly valuable when you are working on projects which have tight schedule constraints. People need the software first, then the performance.
These hacks will be found in the WHack Category.
The day I started learning refactoring, I fell in love with it. I got so addicted to it that I have developed a new habit automatically which not only makes refactoring an easy task, but also saved a huge amount of time when I write some complex algorithm or business logic. It’s a refactoring-integrated process of programming.