Back to the topic.
Code is like a 2X4, or a plumbing fixture. Different methods or preferences are like different brands of the same kind of tools.
Pretty much it's what you make out of them that counts. Having never been a "coder" my sense of pride comes from the end results not the methods. And when I search the web to find new building materials, I will as often as possible use the ones with the fewest lines of code.
I wrote a Sort routine once, one of the few completely original procedures I ever wrote. One of the guys here saw it and offered a criticism having to do with reloading data-set for each record. It was a valid criticism, in a system with a lot of records it would bog fast. It turns out I only used it on low record count tables, so no need to change it.
What a big surprise when I finely did, it took most of a day to rewrite all that. But what a difference it made. So I say use whatever is the easiest to implement, until it conflicts with system performance. And then use that new one over and over.