There's actually two parts of your question.
Part #1 - Resume Perception
One thing a lot of people lose sight of: anything like credentials, github repos, coding portfolios, etc - is simply used as a proxy of "Can this person do the job?"
In other words, if we get an applicant with a github repo that has a decent amount of code or has a .NET Microsoft certification, we're not excited about the specific accomplishments. We're excited because it's a decent indicator that they're capable of doing the job we need.
Once you understand that, the problem becomes much simpler: what things can you do to let employers know that you have coding proficiency? Github's a great one, which potential employers love (since they can go ahead and poke around with how you typically code.) So if you're worried about lynda being expensive, or anything like that - just start doing some coding projects and putting them into GitHub.
Part #2 - Actual Skills
This is going to sound mean, but I'm pretty sure your problem is not that your resume is being perceived badly. I mean, you're getting the interviews... its only when you come in and meet with them that they say "Yeah, that's not who we're going to hire." Your problem is... you don't have the skills needed for the job.
Which isn't the end of the world. Get the skills you want - heck, there are all sorts of 'learn to program' channels on YouTube alone.
The main reason I bring this up is... I'm a bit worried from the tenor of your question. You didn't ask anything about "What's the best way of learning X, Y, and Z?" Everything was from the lens of "How can I make myself look good to companies?" I'd suggest worrying more about getting those skills in the first place.