Maybe you know "better" now? With the experience you have built, you know which problems can occur, which architectures work well, which traps appear in the co

Maybe you know "better" now? With the experience you have built, you know which problems can occur, which architectures work well, which traps appear in the code you read, ... so when you have to take on something, you may be more interested in turning it around, but it's a tough task, and sometimes not even possible due to your company, so you end up being depressed On thing I have become good at with time is refactoring, but when I can't do it properly, don't have enough information, not interested by the subject, or the team, I end up mostly giving up. I think this is kind of being more wise and doing things that matter (to ourselves), instead of just writing some piles of code.