Habits and processes for algo trading?

[analgotrader]

Hey all! In the discretionary trading world, there's a lot of talk around developing good trading habits - do the daily prep, follow your entry checklists, complete a trade log.

I'm wondering if anyone has a set of habits or processes that have helped their algo trading endeavors.

I came across this video, Habits that made me a better quant trader and coder, which lists these habits:

1. Write down 3 - 5 daily tasks that move the needle.
2. Document your code as you go.
3. Prioritize testing and/or getting a second pair of eyes on your work.

For myself, I personally try to write down tasks each day. And I keep something of a research journal. This helps me keep momentum up day-to-day, even if I haven't produced anything tangible.

But are there any other processes, habits or structures I should try out?

 

[fan27]

This may seem obvious, but make sure your algos are running when the market opens. I have had occasions where the market opens, rips higher and I forgot to turn on my algos. When that happens...

 

[zdreg]

Hey all! In the discretionary trading world, there's a lot of talk around developing good trading habits - do the daily prep, follow your entry checklists, complete a trade log.

I'm wondering if anyone has a set of habits or processes that have helped their algo trading endeavors.

I came across this video, Habits that made me a better quant trader and coder, which lists these habits:

1. Write down 3 - 5 daily tasks that move the needle.
2. Document your code as you go.
3. Prioritize testing and/or getting a second pair of eyes on your work.

For myself, I personally try to write down tasks each day. And I keep something of a research journal. This helps me keep momentum up day-to-day, even if I haven't produced anything tangible.

But are there any other processes, habits or structures I should try out?

Your post is the proper way to ask for assistance. You ask for help but you offer something in return without being asked.

 

[themickey]

Gotta learn to chill and let algo just do its thing.

 

[guest_trader_1]

"Test Driven Development", and if you have time to lose your sanity "Behaviour Driven Development".

That will force you to write your code as if you were part of a team. The problem of solo-coding is that you don't have anyone to challenge you, so you are comfortable with a code that would never be accepted in a professional team.

If you follow one of these processes you will see how you have to structure your project properly, just because you are forced to do it.

 

[Heydrrich]

"Test Driven Development", and if you have time to lose your sanity "Behaviour Driven Development".

That will force you to write your code as if you were part of a team. The problem of solo-coding is that you don't have anyone to challenge you, so you are comfortable with a code that would never be accepted in a professional team.

If you follow one of these processes you will see how you have to structure your project properly, just because you are forced to do it.

The positives of solo-coding are that you aren't held back by any dumb managers/programmers.

 

[zdreg]

"Test Driven Development", and if you have time to lose your sanity "Behaviour Driven Development".

That will force you to write your code as if you were part of a team. The problem of solo-coding is that you don't have anyone to challenge you, so you are comfortable with a code that would never be accepted in a professional team.

If you follow one of these processes you will see how you have to structure your project properly, just because you are forced to do it.

"If you want to move fast move alone. If you want to move far use a team."

 

[guest_trader_1]

"If you want to move fast move alone. If you want to move far use a team."

Confucius, are you there?

 

[Coner1980]

"If you want to move fast move alone. If you want to move far use a team."

Good thinking, but in team, we can do more.

 

[chris.page]

I trade primarily futures and run my strategies on a dedicated Windows server using MultiCharts. On Sunday afternoon before the futures market opens I have a pretty standard routine that includes:

• Making sure the previous week's live trades, including slippage and fees, line up with backtesting the same period. You'd be surprised in automated strats how easy it is to write something where live <> backtest trades.
• Apply Windows Updates and restart the server. This is HUGE. I find restarting the server weekly keeps Windows AND MultiCharts AND the IQ Feed client much happier.
• Start up all services AND make sure IQ Feed (market data provider) in online and working.