How to draw up a technical task for ordering an automatic trading strategy?

Generally, there is no universally accepted format for writing a Tech Spec, but based on my extensive experience, I can say that it should be a separate text document file, and here’s why.

Imagine a situation where a client tries to explain a rather complex trading strategy to a programmer in a messenger, such as Telegram, without any prior preparation. Oh, dear! It will take at least 100 messages of chaotic rules, screenshots, discussions, and clarifications. And the poor coder will have to scroll up and down in this chat to piece together the logic, and they will also need to consider all the rule corrections that the client will inevitably come up with as they delve into their own strategy. It’s very easy to get confused here, or to implement logic that has already been changed by the author in lower messages. Even if, by some miracle, the executor manages to correctly reconstruct the logic of the trading strategy, it will take much more time than if the author sits down with a Tech Spec template and fills it out thoroughly and thoughtfully. It’s also worth considering that the developer’s time is not free, but we’ll talk about the cost a little later.

For now, let’s just accept as true that a technical specification is an electronic document in any format that supports text formatting and attaching images. It can be a document in formats such as doc, pdf, and others.

Now that you know it should be a document, are you ready to dive into the details? It’s going to be intense, but I promise everything will fall into place. If you’re ready, then let’s begin!