“the Diagnostics it comes down to uh you break you think down to smaller problems making sure you know what what system is involved in this what's tied into where you a lot of those especially when you go into like older apps where you're just trying to find all the webs and stuff... the thought process of just working down the chain um definitely crosses over”

Carry mechanic diagnostics into code debugging

Treat software debugging the same way a mechanic traces a wiring harness: break the problem into the smallest verifiable subsystem, identify what's tied to what, then walk power-and-ground down the chain wire by wire. If you have a non-coding background, your existing diagnostic instincts are an edge, not a handicap. The discipline to keep tracing past "I don't know" is what compounds into shipped products.