It’s funny, but I often think how similar they are after doing a project. Maybe I haven’t written enough software for it to feel routine, but I often enjoy the unique and unexpected challenges in each that require creative thinking to solve.
One interesting woodworking tip I carried over was “Know your tolerance”, i.e. does it need to be accurate to within an inch, an eighth, etc. I often apply that when working on software now (i.e. how “perfect” and bug free does this component really need to be?)
People often say that “code is malleable” and you can change anything, whereas working with wood and tools is unforgiving. I actually think they’re comparable again, in that your time is what costs the most, and you can fix anything with minor materials cost compared to the time cost. Throwing away a piece of wood I worked on for a while and messed up isn’t much different than deleting a working branch that didn’t pan out. (Working with a contractor makes this more apparent. They’ll happily change almost anything after they’ve done it if you’re willing to pay for it).