You can't. Give it up. You either have the ability to think logically and symbolically or you don't. If you can't handle math then you'll never get beyond writing "hello world" programs.
floating point is really an integer split into sign, base and exponential part. FPU hardware just facilitates floating point math that could be emulated on integer CPU and makes it faster. Internally most operations for all "high" FPU math are just bit additions and bit shifting utilizing specialized hardware architecture. Today computers internally are still so 80'
It depends on how your brain works, this comes easier to some than to others. The best way to learn, is to find something that you can build a passion on. don't start with complicated math functions if you find them dry. The way I learned was to create very simple video games in python, using the 'pygame' library. If you can create a simple Tetris, then I would say you've learnt to program. After the basics, the other languages and complicated math come as a natural function of necessity. It shouldn't take you longer than a month or two, if you're right for coding.
The first program I ever wrote was a "legal chess" move generator. I wrote it in C. I was fifteen years old and read K&R in three days. I think that is the correct way to learn to program. Find something that is so captivating and interesting to you that the effort underneath is not even concious. So what is the best way to learn to speak French? Get head over heels over a French girl that doesn't speak English. You will learn to speak in three months. This will teach you how to "hack". Now, if you have it in you, going from "programmer" to computer scientist requires more than just seeing a computer as a hammer or a screwdriver.
Anybody can learn anything, especially with the resources you can get from the internet. If you want it bad enough, you will succeed. But realistically speaking, you are facing an uphill battle: if you can code in easylanguage, that is not an asset, it is actually a handicap. because easylanguage is a procedural language, you think in step-by-step chain of thought. it is easy, it is logical, it is fast, you see your results immediately. On the other hand, java/c++/c# are objective languages, you think in conceptual terms. it will be a major hurdle for you to rebuild your brain to think in oop. you can learn the syntax of java/c++/c#, that's not difficult. you will be coding in java/c++/c#, but you will find that you tend to code it in a procedural manner rather than in the oop framework. ie. you will not be utilizing the power of an object oriented programming language. In order to fully capture the power of oop, you have to be fully fluent in the paradigm, and that could take years.
There have been a lot of good responses and thanks! A few people have nailed my issue correctly. As WD40 put it, "easylanguage is a procedural language, you think in step-by-step chain of thought" and that seems to be the issue that needs to be addresses. I do think in a step-by-step process and when I try to convert my Easy Language systems to C# I run into object oriented issue that I have never had to deal with.
You don't need to be good at math in order to learn how to program. What you do need to be good at is thinking logically, that is, understanding logical relationships between entities and the logical structure of code. You don't need any math knowledge other than basic arithmetic in order to learn C, Java, C#, and most other languages.
Try Udacity or Coursera. Both have online courses. There is a new course (they add a new lesson every few weeks) on Udacity called Introduction to Programming in Java https://www.udacity.com/course/cs046 Good luck, -David
Math is not exactly the issue. I have no problems building my own formulas because I understand how bars are formed and the relationships between data s. The issue is I never made it past 6th grade and even before that I never paid attention in school. I was a bad student and that is a understatement. The math related issue is math terminology that languages are based on. For example "Boolean vs, Double". To me that is a input or Value. I still don't know how to multiply or divide so Algebra terms are a big issue. I just started on http://www.codecademy.com/ . It seems to be explaining thing easily. Someone like me needs examples to compare terms with. Once I get the concept I can literally spin it and run examples in my head as if it were on a computer screen. I just don't have the educational foundation and learning to many things as I go keeps side tracking me almost as much as Elite trader. If there is a moderator reading this. Then ET should consider creating some resource list based on visitor suggestions. For example a list of good places to learn programming with reviews like the broker section. Besides that it is good for SEO and the user experience. Again, the replies on this tread have been great and not the usual B.S. that is endlessly discussed like indicators and who said, she said. Thanks All!
Are you looking to dig in and become a programmer? Or are you looking to understand stuff so you can confidently call BS if someone is trying to snow you with shit... For someone with a 6th grade education, you read and write much better than most HS grads... Any reason why you haven't gotten your GED (I'm assuming you're in the US && you haven't already gotten it)? Honestly, you didn't miss much after 6th grade. Most school districts are just tax-subsidized day care systems anyways. Self-learning is the way to go. CodeAcademy is probably a good start. KhanAcademy.org is also highly recommended. Regarding moving from procedural languages to object-oriented, you have to remember the main thing - procedural languages teach you how to think/plan/implement logically, in precise detail, and in precise order. You control the app, how it operates, and how the user is supposed to "use" your app. OO, otoh, takes that premise, flips it inside out, and then makes it 3D. The user/external processes control your app, and it's up to you, the programmer, to figure out all the possible ways they are going use/not use/abuse your program, and how your app will respond. With OO, you have to ask more questions, do more thinking, do more planning, ask more "what if" questions.