I recently heard the term “technical debt” used in a conversation about the use of AI in software coding. It refers to “the future costs associated with relying on shortcuts or suboptimal decisions made during software development.”
I suggest that educators and educational leaders experience a kind of “technical debt” when they adopt technologies in their classrooms and schools, and that these debts are not always considered, especially in the glitter and glow of devices that are being marketed to them.
These educators and educational leaders can’t envision the future costs of these technologies because they suffer from the eyeglaze that accompanies these devices.
But technical debt is a real future cost when selecting ANY NEW TECHNOLOGY and educational AI solutions are no different.
What’s particularly frightening with AI, it is so novel that all of these technical debts are not known yet.
In other words, schools don’t really know how the adoption of these technologies will impact future budgets if it is to be maintained. This is especially true since companies like OpenAI and Anthropic have not yet figured out how to profit from their products. This alone, makes all future costs of GenAI to schools unknown.
School leaders would do well to be aware that any adoption of a technology on offer from an Ed Tech company as well as any other tech solutions comes with these Technical debts.
This means being vigilant and skeptical and asking questions about possible technical debt is important, even if it is currently unforeseen.
For example, asking about the profitability of a company can be important as is the current health of that company. Will this company be around 5 years, 10 years?
Educators need technical solutions that are not going to saddle them with technical debts that will consumer even more of the already scarce budgets.
A complete investigation into the solution and the company offering it is vital, otherwise, schools and school districts will find themselves saddled with technical debts impossible to resolve.
No comments:
Post a Comment