Hacker News Reader

Comment by crsv | Hacker News Reader

You have a software engineering job and you never used recursion of any kind? This strikes me as super odd.

I can only think of a couple occasions in my professional career where recursion made more sense than iteration. Both involved traversing trees with unknown depths (parsing XML and scanning a file system).

That hasn't stopped it from showing up in every programming interview I've ever done.

I haven't really used it for anything other than super simple things with a very tightly bound max input. Stack overflow and honestly many recursive algorithms are quite hard to parse in your head especially once you add some edge cases and some other entropy.

> Stack overflow

Well, yeah, other than tail recursion with tail call optimization, stack consumption, if not stack overflow, is always an issue.

> and honestly many recursive algorithms are quite hard to parse in your head especially once you add some edge cases and some other entropy.

I find lot of things are easier to conceptualize recursively than iteratively, though parsing really depends a lot of the language.

I do embedded work. In this field some compilers don't even allow recursion.

They might generally use a library that handles a lot of common usages for recursion, like traversing a tree for whatever reason.

A question I've had in an interview was what is the difference between recursion and iteration. Fairly easy to explain, including examples of usage.

I too never used it. Recursion is usually an inferior solution.

It's almost always a norm that you never use recursion in production code. Always convert it to iteration. Bounded iteration.

Depends on the language too, I suppose. I'd be more shocked if they said they had never used recursion, but were using haskell at work.

Reply on news.ycombinator.com