/explore
|
You are here 
|
gavinhoward.com | ||
| | | | |
hashrocket.com
|
|
| | | | | One of the biggest challenges around technical debt in software development is how to communicate its true costs to stakeholders and decision-makers. The first part of this two-part series on technical debt explores some ways it can be helpful to think of technical debt like financial debt. | |
| | | | |
lukerodgers.ca
|
|
| | | | | (This piece is a work in progress, a placeholder for developing thoughts on technical debt and measuring the performance of software development teams. I will update it as my opinions change.) An oft-cited benefit of paying down technical debt is that it will allow you to move faster. This is typically characterized in terms of... | |
| | | | |
labzero.com
|
|
| | | | | Technical debt is a natural part of the software development world, but it can hurt you if managed poorly. The two main sources of technical debt may surprise you. | |
| | | | |
www.jurecuhalev.com
|
|
| | | Grokking Simplicity is an introductory book that will take you to the world of functional programming. It uses basic JavaScript to explain filter(), map(), and reduce() in simple and logical steps. As an experienced engineer, I read the book hoping it would allow me to read F# code better. What I got from it instead [...] | ||
