It’s always the journey that matters.

If you’re experienced as you are, you’re not learning the same way a junior assigned this might learn from it.

So the project I mentioned while I did write every single line of app code and IAC, made every architectural decision, etc., I did come on an off the project over the course of a year and I couldn’t even remember some of the decisions I made.

I also used Codex and asked questions about how the codebase worked to refresh my own memory. Why wouldn’t a junior developer do the same?

I mentioned that I had Codex describe in detail how it debugged it. It walked through each query it did, the lines of code it looked at and the IAC. It jogged my memory about code I wrote a year ago and after being on other projects

	▲	grebc 14 minutes ago \| parent [-]
		If you’re 50+ as you intimated in your first post then you have a wealth of knowledge that juniors don’t. Just because it worked this time doesn’t mean it always will. If you need further explanation of why you might want to spend more time resolving a bug to learn about the systems you’re tasked with maintaining then I’m at a loss sorry.