> You know how it is, code calls other code, and logically it forms a tree of calls and return values that often goes several layers deep. I struggle to hold mo

> You know how it is, code calls other code, and logically it forms a tree of calls and return values that often goes several layers deep. I struggle to hold more than about 2 levels of this call stack in my head. By the time I'm down in the weeds I've forgotten what I'm doing, what the purpose of the actual API call is. I also had that difficulty when I was a younger developer. The difference now is that the novelty of learning how to program at a professional level, learning a new language, and learning a new framework, isn't there. Instead, the novelty comes from convincing others not to make the mistakes I would have made 20 years ago; and not making those same mistakes myself. I was in your shoes, things I'd find frustrating are: - The original version was working fine; a rewrite just isn't justified. - Some team members are writing poor quality code, and I just can't convince them to do it right. - The original version has style / habits that make it fragile or hard to understand. - The original version has behavior that's generally not understood.