New
We have updated our Terms of Service, Privacy Policy and Terms of Use. Review.
Back to Blog
Some thoughts on technical debt

Some thoughts on technical debt

Lorenzo Frattini

There are two types of mistakes all developers make:

  • Those you can live with indefinitely
  • Those you can live with for now, but that you have to fix at some point.

I want to talk about these today.

There is research that shows how remediation costs grow through different stages of the development lifecycle. The later you fix, the greater the cost.

At Clayton, we look after a lot of Salesforce code. Data tells us that a team of 6 developers accrues on average 67.5 hours of future rework every week, 1,485 hours every month.
This capacity - 17,820 hours/year - goes to waste.

It's not because they aren't skilled, nor because they are lazy. In fact:

  • Most are experienced developers
  • Most are Salesforce certified
  • Most run PMD before they commit
  • Most do peer reviews

Yet, priorities and deadlines make people cut corners sometimes.

We can look after your team and automate this out of existence, so that you get your code first time right, ship faster, rework less.

Share on social media: 

Get ahead.

Join 1000+ Salesforce professionals who receive critical reading, insights and expertise written just for them, from the team at Clayton. Once a week.
Unsubscribe with one click.

More from the Blog

Making your boss care about technical debt

It's not always easy to get your boss on your side to take action against technical debt. Here are 3 things your boss will most certainly care about.

Read Story

Understand, Assess And Manage Your Salesforce Technical Debt

Our first handbook looks at the state of technical debt in the Salesforce ecosystem and contains tips on how to address it.

Read Story

What we learnt scanning 10.2 billion lines of Salesforce code

As we hit our first 10 billion lines of code reviewed, we look at some of the things we have learnt about the Salesforce ecosystem.

Read Story