Current Mql4 Coding level: Average/Intermediate
I have a valuable idea to approaching learning Mql4 at a faster rate us Novice Coders:
- We form an Mql4 skype group.
- We ascertain what level of knowledge we’re all currently at.
- We read from the “Mql4 online Book” and “Mql4 Documentation” together.
- We choose a specific content to learn: (Functions, Arrays, Variables, Structures, etc).
- We implement practicing what we’ve gathered from the literature’s material.
- We repeat this process until we’ve mastered that specific coding area then move onto the next.
- We share, implement, practice, read, and continue to motivate one-another and hold ourselves accountable until we’ve learned the entire mql4 language.
- Optional, if an experienced Coder wishes to be elected as the Moderator and Leader of the Skype group, he/she can. They must carry a Leadership mentality, and
must be willing to recommend and organize structurally what content he/she feels the group must read to optimize our learning curve.
Any thoughts, recommendations, or opinions on this approach?
2 Likes
What’s your take on learning MQL4 vs MQL5? If someone started with a blank slate would you recommend they start learning MQL4 over MQL5?
It’s a shame this topic will get buried over time in the beginner section area. This would probably last a lot longer if it were posted in #trading-systems:expert-advisors-and-automated-trading
Well, allow me to clarify some things:
-
I call myself a Novice/Average because it trains my mind to never embrace “ego” or “self-centeredness”. The moment one deems themselves a master, they shut off the learning part of their brain. I am in essence, not a Novice Coder though, but I refer to myself as such to remain open to learning.
-
Regarding Mql4 over Mql5, you definitely should learn Mql4 first. (That’s without doubt) Then from there, move into Mql5.
-
I propose reading the mql4 documentation with other members because it creates an opportunity for teaching (which I love to do) and further learning for myself. (Though I’ve read the documentation and book more than once). Someone might see something I may not have not picked up on the first or subsequent reads through the Book and Documentation.