I’ve been working on and waiting for this paper to get published. I co-authored it with some of my team mates in Pivotal/Tanzu Labs. It documents a practice that the Labs people have been doing, a developer toil survey. First, we develop the concept of “developer toil” in the paper. I think it’s a type of tech debt that isn’t noticed and optimized enough: all the work and waiting developers need to go through to finally start coding and running their software.
Oftentimes, we get clients who will say, ‘We need to assess those 10,000 applications that we know have to go to the cloud before we do anything on them.’ And we try to change that around and ask why: ‘Why do you have to look at all of them?’ . . . I haven’t found a customer that doesn’t know some of those critical applications that are very painful, that go down all the time or whatever the criteria is.