# So you want to climb that tree?

I have been feeling a bit nervous lately that I am not skilled enough to solve tree (data-structure) problems. Not only on the interview prep side but also while writing application code. It is true! I failed to identify a problem as a tree problem while at work once and ended up writing a monstrous function that somehow got the job done. By the time I realized it was too late to implement/reimplement it. (However, the feature works! it still does :D )

So here it goes! My effort to get good at identifying and solving tree problems. In fact, this effort started quite a while back, but I guess writing this document will help me and anyone else looking to get a framework for attacking tree problems.

Also, this document is better suited for people who have already taken up a computer science course or encountered trees. If that is not you, I heavily suggest reading through some basics) about tree.

## Types

There are different types of trees. So it might be worth taking time to explore a bit on getting idea about different kind of trees.

In case of interviewing, you will often encounter these more

- Binary Tree
- Binary Search Tree
- AVL Tree

There are a huge number of tree types that you could encounter while writing applications. I have noticed common occurence of N-ary trees in practice.

## Traversals

Step 1 is getting good at tree traversals. I have already done my practice in this section by writing up this blog post and solving some problems related to them.

Key here is to know both the recursive and iterative approach for solving the traversal problems. Going top list down the set of leetcode problems here. If you could solve the below problems in both ways, you are good to go to the next level!

- Binary Tree Preorder Traversal
- Binary Tree Inorder Traversal
- Binary Tree Postorder Traversal
- Binary Tree Level Order Traversal

ufff! You are done with it. What’s next?

This is good NEWS. By this time, given a tree problem, the first question that you would ask yourself should be

1 | ____________________________________ |

Once you are done with binary, try N-ary trees. This is gonna be so easy for you. Also this is a proof that if you get good at binary trees, you can face other kind of trees with a little confidence.

- N-ary Tree Preorder Traversal
- No in-order available because there is no answer to “after which children will we visit the root node?”
- N-ary Tree Postorder Traversal
- N-ary Tree Level Order Traversal

These problems just vary in the way their child visitation is implemented.

1 | if (curr->left != nullptr) |

and

1 | if (curr->right != nullptr) |

You could basically use this knowledge to attack on some general tree problems like the below.

- Binary Tree Zigzag Level Order Traversal - Supplement level order with a stack and you are done!
- Binary Tree Right Side View - Do a level order traversal and add the last element of each level to the result
- Binary Tree Level Order Traversal II - Supplement level order traversal with a stack to capture the level order in reverse order.
- Invert Binary Tree - Post-order traversal the nodes and invert if any of the child is present.
- Binary Tree Tilt - Post-order traversal to save the sum of subtrees in a map and pre-order traversal to compute the tilt of each node. (recursion might only need a post-order + a global variable)
- Binary Tree Vertical Order Traversal - Level order traversal with a pair<TreeNode*, int> (int contains the vertical level information) + use a map<vector
> to store the results.

## Depth

The depth of a node is defined as: the number of edges between the node and the root.

Note that leetcode and some other places consider the count of nodes instead of edges while computing the depth.

- Maximum Depth of Binary Tree - classic level order it. :D
- Minimum Depth of Binary Tree - Level order traversal + return the depth of the first leaf node.
- Maximum Depth of N-ary Tree - classic level order again :D

## Bye!

I have to abruptly end this post now. Because I am lagging a bit in stamina and I have to recharge before further attacks :D

I solved most of the above problems continuously over a Saturday. ah, that felt good. Today is Sunday and I think I should just post this out in my blog for now. I actually feel pretty good about it! My leetcode rating went from 2 to 2.5 :D (yay!)

There are still common tree problems floating around us, which I haven’t listed and solved yet. (like the diameter of a binary tree). But keeping them for some other time. Until then, bye!