RT @SahajSoftware: The modern Kubernetes cluster hosts a range of services. An URL masks the complexity of microservices. What lies beneath….

RT @unclebobmartin: The Single Responsibility Principle (SRP):. Gather together those things that change for the same reasons and at the sa….

RT @YogiKulkarni: In other words… . Identify and focus on the few major factors that affect a problem… and ignore the minor factors. In m….

Flow in #softwaredevelopment can be increased by minimising the work items being blocked or queued and ensuring work items are being worked on continuously to completion.

RT @GergelyOrosz: When people share how crypto can bring payments to underserved communities, I ask them if they heard of UPI which did thi….

What is your definition of the duplicate code? Is it the code that looks identical/similar now? Or Is it the code that looks identical now and also changes together for the same reason? If it's the latter then what is the best time to remove the duplicate?.

RT @YogiKulkarni: Many developers severely underestimate the complexity involved with microservices. While there are many books/articles a….

RT @_mekin: Creating a thread for this question from @vamsi_edu - How do you assess ownership in an interview ? (1/n).

RT @YogiKulkarni: We've been running a learning competition called "Big-O" at work. This time it was about building a high-performance ke….

RT @david_das_neves: A quick intro to Linux. Great for starters and young professionals!.[Guide] Linux SysOps Handbook..

RT @confluentinc: 🚨 Free eBook! 🚨. Learn how service-based architectures and stream processing tools can help you build business-critical s….

RT @samnewman: Well, the 2nd edition of Building Microservices is off to the printers. Ebook release in about a week, print books arriving….

Reading a new #code base with depth first approach goes against the idea of Abstraction. Breadth first approach for understanding a new code base is a better approach. #programming. .

Sharing of common code / state and sharing of common interface / type are two different things. Common code sharing can be achieved with Composition or class inheritance (prefer composition). Common interface (substitutability) can only be achieved by (interface) inheritance.

Instead of focusing on the number of lines per method, I like to focus on the number of local variables per method and try to reduce them. #programming.

If you follow the package per layer approach, then minimize the number of packages changed per layer.

For this to work better, smaller classes which are focused on a single thing help (SRP).

Idea is to minimise number of packages that should change for a given feature change. Do this regularly within the team and you should have well-defined package/module boundaries.