Done.
I was so wrong. This was nothing like riding a bike. Or maybe it is. I haven’t ridden one in years.
Glad I’d uploaded that gif in the Notion thread. The field headers and data formats ensured I didn’t have to touch or source anything from Notion. Plug & play all the way.
Very proud of this part. As a coding noob I’m feeling a bit arrogant right now. Justifiably so.
Two marked efficiencies over previous code:
- Previous delimiters were hardcoded within a Printf() string. Not this version. CSV delimiters can be changed now within the FILEOPEN function.
- Previously there were individual For Next loops against each group of arrays (each of the indicators, 10H/L values, OHLC values). This was because I was strictly enforcing the logic in the MQL5 manual samples and whatever code I could find online. Chucked it and figured a workaround when I realised this time round that most of my arrays were one dimensional because I was only looking at previous day values only. That helped streamline the code. I was procrastinating at the prospect of coding and error checking those loops again. It’s amazing how a want to be lazy can motivate innovative ideas sometimes.
I’m pretty sure there my code’s far from efficient in the eyes of a seasoned MQL5/C++ coder. But this is my Frankenstein and I’m proud of it.
Notion Checklist.csv (10.4 KB) Notion Checklist MQL5 code.txt (5.1 KB)
Restored Balance
The code is super important. This code enabled a process that I built a rigorous daily routine around. Challenging enough that I never once completed my daily checklist:
I’m naturally headstrong and relentless. Good traits for problem solving but naturally bad when the same traits leads to a propensity to overtrade, revenge trade & chase profits. Atleast the same equivalents when I played poker.
The routine building was to adapt to a more compartmentalized approach. It was to force efficiency and economy of mental capital (termed by Alexander Elder) over time. With the intention of adding onto it or changing it when things got too comfortable. To shock the system.
In hindsight, it might’ve been worth it to have paid for a data recovery tbh. But not having it had forced a re-evaluation of what I was doing. I expect a more robust approach to my previous routine.
Possible New Projects
Now that I’ve just finished the coding exercise and have built a library of sample codes to make future coding easier. I should be able to:
- take on building a data extract for the historic MT5 economic calendar data.
- build code for adhoc data extracts. Recently needed ATR values to run some numbers. Was forced to let go because the time required to invest in learning code for that requirement wasn’t worth it. Now it’s a very simple exercise.
Reading:
Decided to start with Disciplined trader and work my way up to later books. Dismal progress. Let the coding take most of my time and just went through 40 or so pages so far.
Surprising MQL5 discovery
Was going over some pretty good MQL guides like this one and decided to check the author bio for this one. Was surprised to see he’d coded the following:
Pretty cool that he’s created EAs on Thomas Bulkowski’s findings. What’s interesting is whether the basis for those indicators can be used to update/continue his studies, given that the book was published nearly 2 decades ago.