> I did eventually get a moderately complex program to work. But basically 
> every time my program didn't work, I'd replace the implementation with an 
> equivilent but differently worded one until the program actually worked.

This is the sort of thing I was referring to when I said you need to know 
what you don't know about your code. You can't just guess your way to an 
understanding; you must first learn why your original code is broken. This 
isn't always possible but it's a good goal. You learn a lot more that way.

> 1. It was 10 years ago, not 20.

Surely the things you've learned about programming in the last 10 years 
would be helpful. Personally, I failed to learn C++ the first time I tried 
but succeeded the second time after years of working with other languages.

Anyway, if you're not interested in learning C++, that's cool. I had thought 
you were interested. I just see a pattern in your posts where there are 
things you want (in this case a programming job), and when people encourage 
you to get them, you list reasons why you're not able to, or why it's 
difficult. You need to learn to ignore or deal with the hurdles and push 
yourself until you get where you want to be.

 - Slime
 [ http://www.slimeland.com/ ]

Post a reply to this message