Yet another recurring phrase on DotNetRocks’s podcasts, and a catchy one at that! The term ‘technical debt’ was coined by Ward Cunningham to describe the eventual consequences a software development organization incurs when it chooses to do things the quick and dirty way, which benefits the short-term but increases complexity and ultimately is more costly in the long term.
Technical debt incurs interest payments in the shape of extra effort required for future development, but can be paid down by refactoring the quick and dirty design into better designs. It costs to pay down technical debt, but you gain by reducing future interest payments.
Technical debt is almost unavoidable in any real-world development project, and sometimes it may be sensible to incur some technical debt in order to meet an important deadline just as businesses incur some debt to take advantage of a market opportunity.
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong