Double again - and those things can (should) change again. It's not so much a 'bow wave' of technical debt as a constant incoming series of waves. It's the job.
The good part is, technical debt can disappear too. Reimplement an account authorization scheme with a new service, and all those old tickets for the slapdash buggy version can disappear. And so on.
"We started slowly shifting from every engineer on the team knowing everything about all the code, to the minority of the team having that legacy knowledge, to nobody on the team that knew about everything."
God I hate this. Nature meant for us to carefully tend our code for ever and ever doing tiny changes every forth year. Not trying to grasp eachothers' wicked minds.
"The product that began as a bowl of digital spaghetti has transformed into a collection of well-tested microservices that can scale to collecting tens of terabytes of configuration data."
I really can't believe that being 1% truthful. Note first quote.
Looking back on those days I miss them, but during the actual process of it I was stressed, scared, and totally unsure of myself. It would be interesting to go back into that stage with the knowledge I have now.
This may be the case some, but not for others.
I was someone who worked hard and enjoyed trying to get better. The company never rewarded me, instead outsourcing my job and forcing me to basically start over... and over. Now I'm less knowledgeable about things that matter, and less employable. It was a waste of my youth.
