Hi All
How will you cope with technical debt in the shape of cryptographic debt - think current Software practices and APIs and then onto Quantum Cryptography as well as Q-Day.
Technical debt in software products typically results from unavailability of technology or unavailability of time.
It is the concept of “ship first, fix later.” There simply isn’t the time or manpower to do it right the first time. And nine times out of 10, the quick and dirty turns out to be “just fine.” It may not be elegant, not performant, but “fine” nonetheless, which is why the practice is near universal in the software world and technical debt is pervasive.
A most interesting piece and certainly something to think about.
Regards
Caute_Cautim
@Early_Adopter Well it runs in parallel with the forthcoming Q-Day and planning, if organisations are not planning, technical debt could be incurred due to not being prepared or not realising the implications of doing any testing, migration in a controlled manner.
Regards
Caute_Cautm
@Early_Adopter Well if the industry messes up the crypto migration, you may be paying for the coffee with Roman Tin coins or Pay forward or something similar or using a bartering for services system.
It needs a lot of careful planning, testing, and staging.
Regards
Caute_Cautim