In my previous post, I discussed the concept of tech debt and its various classifications, including code debt, architecture debt, and security debt. I also covered some of the metrics …Managing Technical Debt: Strategies for Identifying, Balancing and Pitching to Product Owners Read More
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 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
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