Nirmal Kumar’s Post

The article is about Open Closed Principle.

A good article which deserves to be read

Ignore the title. Interesting topics and facts inside. ( with links )

My first article 😳

Hey Igor Zalutski, this evening I noticed that ThePrimeagen was reading an article about a company that rewrote their systems from Python into Go. Naturally, I clicked in because I love these kind of articles. As he was reading, I found myself silently nodding along and agreeing with the author's points regarding rewrites, their risks, and the reasons they happen. It's true, so many people undertake rewrites and experience utter failure, but with so many exceptions to the rule published online, it can cultivate false hope... but just sometimes it still proves to be the right choice. Still nodding along, it was when ThePrimeagen read this sentence that my jaw almost hit the floor: "Apparently people not only care what Digger is written in; they cared specifically whether or not it is in Go." I did a double take, paused, and rewound the video to confirm my suspicious: It was your article all along! Digger, the open source alt to Terraform Enterprise. Really great stuff, and just shy of the coveted GitHub 1000 stars! https://lnkd.in/gTpDqNbY Congrats on the #python to #golang rewrite; if I get the chance, I'd love to make a PR. Although, long gone are our #palantir days where I was approving your code on the #airbus project in Toulouse; now, I'll have to seek your approval for mine, haha. Regardless, it was a pleasant surprise to hear your article featured this way and I wish you all the best for Digger. Great work! https://lnkd.in/gHp46_nx

Check my first blog.

Here is my new blog , Have a look 😀

Check out my new article!

Check out my article on Medium!

About code comments: I was used to the idea that a good code should have comments along code lines. I changed my mind after reading <Clean Code> by Robert Martin, a great book. Expressive names for classes, functions, and variables look lengthy but are good enough to show intentions. Comments may indicate poor namings or even a poor design of code structure that too many responsibilities are desired. Code will evolve but comments are usually not. Over time, legacy and sometimes misleading comments liter around. It can cost readers precious time to understand the code. PS: please subscribe our new EQdyna Substack for news https://lnkd.in/gNCq9xEy