Creating technical debt for your Salesforce system isn’t the end of the world; it’s an unavoidable necessity. Ward Cunningham, the American computer programmer who coined the term, maybe said it best back in 1992:
“Shipping first-time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite… The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt.”
Decades before cloud-based systems and digital transformation became the norm, Ward recognized a basic truth of development–technical debt is inevitable, but it shouldn’t be unmanageable. Just like any financial loan, it needs to be accounted for and paid off promptly.
We know technical debt isn’t a new concept, but it always deserves revisiting. That’s why on the heels of our 2020 Salesforce Talent Ecosystem Report we felt an obligation to explore technical debt in the context of evolving demands for Salesforce talent, particularly two interesting anomalies:
- Declining demand for Salesforce Architects
- Global demand for developers is outpacing architects.
To continue reading, head to Salesforce Ben for the full post.
