If you build with the explicit goal to learn and explore the process and problem domain, and then have to rework code because of new insights and understanding,

If you build with the explicit goal to learn and explore the process and problem domain, and then have to rework code because of new insights and understanding, we are as close to the original definition of technical debt. But it is my impression that this is the rare exception. In most cases, people are just bullshitting to cover up their ineptitude.