Prashant Kalkar (@kalkarprashant) profile picture
Joined September 2013
Photo by Prashant Kalkar (@kalkarprashant)
Prashant Kalkar retweeted
The modern Kubernetes cluster hosts a range of services. An URL masks the complexity of microservices. What lies beneath the hood? This Devday join @kalkarprashant at our Pune office or PUN - tinyurl.com/2p8p9vu4 CHE - tinyurl.com/3twaswun BLR - tinyurl.com/2p8mbpj5
1
2
4
The Single Responsibility Principle (SRP): Gather together those things that change for the same reasons and at the same times. Separate those things that change for different reasons or at different times.
10
84
7
440
Prashant Kalkar retweeted
In other words… Identify and focus on the few major factors that affect a problem… and ignore the minor factors. In most cases only few things are disproportionately important. Ignoring this leads to sloppy thinking.
Given a complex problem: “Imagine two people: - Person A acknowledges the complex problem, and focuses - Person B doesn’t see the complex problem, and simplifies. Who is more likely to make progress? My money is on A.” - @johncutlefish Brilliant. cutlefish.substack.com/p/tbm…
1
1
5
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.
3
Prashant Kalkar retweeted
When people share how crypto can bring payments to underserved communities, I ask them if they heard of UPI which did this - but without blockchain. UPI has no fees, is secure, works offline as well and 6 years after launch accounts for 60% of retail payments in India (!!)
87
598
72
3,493
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?
Prashant Kalkar retweeted
Many developers severely underestimate the complexity involved with microservices. While there are many books/articles about the topic, they often miss sharing intuition about the huge level of complexity involved. Will try to share my understanding in this thread...
54
381
67
2,076
Prashant Kalkar retweeted
Creating a thread for this question from @vamsi_edu - How do you assess ownership in an interview ? (1/n)
Replying to @_mekin
Any specific markers or interview questions which worked best for you to check on this?
5
16
8
62
Prashant Kalkar retweeted
We've been running a learning competition called "Big-O" at work. This time it was about building a high-performance key-value store. Here's the problem statement https://teapawt.net/t.co/1Nm6Qga8nv created by @priyaaank.
3
6
4
29
A quick intro to Linux. Great for starters and young professionals! [Guide] Linux SysOps Handbook buff.ly/3KjWlHM #Linux #Learning #OS #DevOps
6
313
4
1,057
🚨 Free eBook! 🚨 Learn how service-based architectures and stream processing tools can help you build business-critical systems in 2022! Download Now! ⏰

35
215
6
2,316
Prashant Kalkar retweeted
Well, the 2nd edition of Building Microservices is off to the printers. Ebook release in about a week, print books arriving in the US and EU/UK in around 3-4 weeks.
24
28
4
341
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. .
1
1
6
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.
1
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
3
Classes that change together should be packaged together. So from next time onwards, before merging your feature changes, look for opportunities to move classes around so that overall fewer numbers of high level packages are changed.
1
2
For this to work better, smaller classes which are focused on a single thing help (SRP).
1
If you follow the package per layer approach, then minimize the number of packages changed per layer.