One of the creative differences I often discuss with software teams is the distinction between technical debt and technical burden. You’ll be familiar with the first term, but I’ll review it here anyway. The second term - technical burden - is one that I use (perhaps I coined it) for a pattern of development often overlooked as a strategic choice.
Technical debt and technical burden
Technical debt and technical burden
Technical debt and technical burden
One of the creative differences I often discuss with software teams is the distinction between technical debt and technical burden. You’ll be familiar with the first term, but I’ll review it here anyway. The second term - technical burden - is one that I use (perhaps I coined it) for a pattern of development often overlooked as a strategic choice.