Clean Code

white framed glass window
Clean Code / Code Analysis / Refactoring / Tech Debt

The Broken Window Theory

- by Shaunak Sontakke

The Broken Window Theory states that when an issue, such as a broken window, is left unaddressed, it sends a signal that the system is not well-maintained and further issues are likely to occur. This concept can be applied to software engineering, where neglecting technical problems and technical debt can lead to a vicious cycle of decreasing codebase reliability and performance. In this post, we’ll explore the implications of the Broken Window Theory in Agile development and offer strategies for continuous improvement and proactive management of your codebase.

The Broken Window Theory Read More
Awesome Architecture
Clean Code / Speaking Mind

Awesome Architecture

- by Shaunak Sontakke

Awesome architecture is something that – I can build, test, and shop my feature within a week.
– I use data to learn from it and my improved version is live in week two

Awesome Architecture Read More
Naming Convention Word Cloud
Clean Code

Importance of correct naming

- by Shaunak Sontakke

I am putting my experience about importance of correct naming. I feel correct naming is the key in deciding object’s responsibilities (methods, variables). Developers frequently hear that “not to spend …

Importance of correct naming Read More
is-a vs has-a
Clean Code

Composition vs Inheritance

- by Shaunak Sontakke

This article will help us to understand when to use composition and when to use inheritance. Most of the cases composition is preferred over inheritance. Inheritance Composition IS-A Relationship Has-A …

Composition vs Inheritance Read More