| A random day's schedule might look like this: |
| 9:00 - 9:30 |
| On the way to the office, start the day by making short-, medium- and long-term plans and priorities |
| |
| 9:30 - 10:00 |
| At the office, read e-mails, check market trends and fix the little problems which might have occurred during the night |
| |
| 10:00 - 12:30 |
| Identify areas of the market where new ideas should be implemented and tested; read literature, search Google for open source components, look into the mathematical and IT details of the problem |
| |
| 12:30 - 1:00 |
| Lunch break |
| |
| 1:00 - 3:00 |
| Shape the identified plan into tasks of reasonable complexity |
| |
| Sometime during the day |
| Interact with traders, other researchers and information technologists during the day |
| |
| 3:00 - 5:00 |
| Start "bugging and debugging" (i.e., programming and testing the code); try the procedures of some known or similar models and check consistency of the results |
| |
| 5:00 - 7:00 |
| Finally, test new models and back-test various operations |
| |
| Around 7:00 |
| Catalogue and memorize the issues of the day, especially if they were conceptual |
| |
| Later at night |
| Sometimes, a solution for one of today's problems is found; if so, it will be implemented safely tomorrow |
| |
