So what's your point?

So technical debt, and this is actually, it's like the motto of our company is regenerate, don't patch.

So through the history of coding, software coding, people would patch code, right? So that means they write the code and then they edit a few lines and they patch it, right? Very much like you patch a shirt.

And the reason why you would do that is because the cost of code is really expensive, right? And so you don't want to throw it away.

This is like a shirt.

Like if your shirt is really expensive, you're not going to, you're going to hold your shirt, you're going to patch it, right? But I bet you, you don't have any clothing today where you have patches on there.

And the reason why is because the clothing has gotten so cheap, it doesn't make sense to patch.

So in your point of view, what exactly is problem-driven development, and how is it different from five coding?