Discussing the article: "Market Simulation (Part 03): A Matter of Performance"

New comment
 

Check out the new article: Market Simulation (Part 03): A Matter of Performance.

Often we have to take a step back and then move forward. In this article, we will show all the changes necessary to ensure that the Mouse and Chart Trade indicators do not break. As a bonus, we'll also cover other changes that have occurred in other header files that will be widely used in the future.

For several weeks, we have been developing some of the applications we will actually need. However, when I began implementing a new application, which will be introduced soon, problems started to arise. The system performance dropped significantly compared to what had been observed until then. Since I do not intend to build the system monolithically, that is, as a single block, it became necessary to analyze and identify the causes of this performance degradation.

While studying the flowchart, I noticed some gaps. These gaps need to be closed because sooner or later they will generate problems. Therefore, resolving these issues and preventing them from recurring is also part of the final application development. While studying the flowchart, I noticed some gaps. These gaps need to be closed because sooner or later they will generate problems. This flaw had gone unnoticed, but upon closer examination, it was detected and corrected. And you, dear reader, will be able to see exactly what it entails.

This kind of detail, often omitted or unexplained by others, can lead aspiring professional programmers to erroneously believe that programmers never make mistakes, or that code is born flawless and develops without errors. In reality, no code - no matter how carefully planned - is free from errors. My hope is that this article, beyond being explanatory, serves to demonstrate the following: code is never truly finished. There is always something to improve or correct.


Author: Daniel Jose

New comment