I haven't even read the article but the way I use this is to familiarize myself with new stuff. You can't plan a system when you have no idea how it's going to work. That's why it's called discovery, you just write code and see how things work, then you refactor or just throw out everything and start from scratch once you feel ready to actually build the thing.
If you just write whatever you happen to come up with and keep it that's just regular code monkeying.
It's also not a technique you use for an entire system, hopefully you're able to plan most things. But maybe a part of it integrates with a complex api you haven't used before, then it's nice to just take some time to figure out how that api really works at a level that's hard to achieve just by skimming the docs.
If you just write whatever you happen to come up with and keep it that's just regular code monkeying.
It's also not a technique you use for an entire system, hopefully you're able to plan most things. But maybe a part of it integrates with a complex api you haven't used before, then it's nice to just take some time to figure out how that api really works at a level that's hard to achieve just by skimming the docs.