I wish I understood the "grain" in programming better. It's a lifelong search.
- copy/paste. You made one perfect table leg? Great, now make another 3. From scratch
- undo. Cut that plank a bit short? Start again
- incremental changes. Want to change the angle of that join? Start again
- imports. Don't want to make those fancy doohickies that go along the edge? You could try to buy some but it's not like there's an international database where you can pick and choose often for free
- debugging. Oh, your wardrobe just fell in a heap when you installed it? Hopefully you can salvage some of the materials and then figure out what went wrong
I'm not a very good programmer either, so I'm sure there's more
Carpentry is reasonably attractive in terms of actual work, so that if it payed as well as software development, many people would want to take it up. My point is that a larger portion of the population would have the necessary ability (and, I assume, inclination) to become a competent carpenter than a competent software developer.
Whereas smacking a few bits of wood together (framing) gets you in the door as a carpenter. But there's a whole bunch more to learn if you're going to do fine woodworking. However, you can be productive form day one if you're willing to learn. That's the same as being a developer these days.
People will pay for low end skills because they are still a skill. You have a comp engineering degree. What are you working on in your job? Does the education fit the work, or on reflection do you have a little too much qualification for the work you're doing?