Tech debt refers to the cost of maintaining a software system over time due to trade-off between delivering software quickly and the long-term cost of fixing issues. It has several classifications including architecture debt, code debt, developer efficiency debt, stability debt, security debt, documentation and maintenance debt, technical product debt, and infrastructure debt. Metrics for measuring tech debt include defect density, code complexity, time-to-market, maintenance costs, technical debt ratio, cost of rework, cost of lost opportunity, cost of maintenance, cost of training, cost of recruiting, user satisfaction, and security metrics. The next post will discuss practices to manage tech debt.Understand your tech debt to manage it better 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
Just finished. Summary: https://motamem.org/wp-content/uploads/2018/10/Good-to-Great-Jim-Collins.pdfGood to Great by Jim Collins Read More
There are many a times where I had to run commands across all docker containers. Here is an handy script to do that: $ cat runCommandAllDockers.sh for container in `docker …Run Command across all docker containers 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