I don't really write code that traverse trees that often these days. I do use libraries or services (e.g. SQL databases) that do though.
And I have no idea whether the implementation of map/reduce I use is implemented as a recursive function or not, I just use it.
If your friend works with implementing libraries or database engines I would be a bit shocked. If he implements applications and services I could agree that keeping things simple and not inventing your own frameworks could be a good idea.
And I have no idea whether the implementation of map/reduce I use is implemented as a recursive function or not, I just use it.
If your friend works with implementing libraries or database engines I would be a bit shocked. If he implements applications and services I could agree that keeping things simple and not inventing your own frameworks could be a good idea.