report: address a few FIXMEs
This commit is contained in:
parent
52bc23c554
commit
05f6ab2845
20
report.md
20
report.md
|
@ -174,8 +174,7 @@ scenarios.
|
|||
we can start taking multiple measurements. The main one that IMC is interested
|
||||
in is wire-to-wire latency (abbreviated W2W): the time it takes for a trade
|
||||
to go from a trading strategy to an exchange. The lower this time, the more
|
||||
occasions there are to make good trades. FIXME: probably more context in my
|
||||
notes
|
||||
occasions there are to make good trades.
|
||||
|
||||
* Analyze the measurements: the global execution team has some initial
|
||||
expectations of the gateway's performance. A divergence on that part could mean
|
||||
|
@ -342,10 +341,9 @@ the gateway binary in order to instrument it under different scenarios.
|
|||
|
||||
I worked on writing those components in a way that was usable for the benchmark,
|
||||
making sure that they were working an tested along the way. One such component
|
||||
was writing a fake version of the RDS (FIXME: what does it mean again?) that
|
||||
would be populated from the benchmark scenario, and provided the information
|
||||
about financial instruments to the gateway in order to use them in the scenario,
|
||||
e.g: ordering a stock.
|
||||
was writing a fake version of the RDS that would be populated from the benchmark
|
||||
scenario, which provided the information about financial instruments to the
|
||||
gateway in order to use them in the scenario, e.g: ordering a stock.
|
||||
|
||||
I went on to write a first version of the benchmark framework for a specific
|
||||
gateway and a specific exchange: this served as the basis for further iteration
|
||||
|
@ -368,7 +366,7 @@ framework.
|
|||
I have delivered a complete, featureful product from scratch to finish, complete
|
||||
with documentation and demonstration of its use. This is at the heart of our
|
||||
schooling at EPITA: making us well-rounded engineers that can deliver their work
|
||||
to completion. FIXME: wax a bit more poetics
|
||||
to completion.
|
||||
|
||||
## Acquiring new skills and knowledge
|
||||
|
||||
|
@ -545,7 +543,7 @@ results directly in more profits being made.
|
|||
|
||||
During my internship, I got to work on a large code base, interact with smart
|
||||
and knowledgeable colleagues, and tinker on what constitutes the basic bricks of
|
||||
IMC's production software (FIXME: phrasing).
|
||||
IMC's production software.
|
||||
|
||||
Working at IMC was my first experience with such a large code base, a dizzying
|
||||
amount of code. It is impossible to wrap you head around *everything* that is
|
||||
|
@ -599,9 +597,9 @@ correct tool set to deal with those problems.
|
|||
|
||||
## Introspection
|
||||
|
||||
Working abroad, with the additional COVID restrictions, is a harsh (FIXME: find
|
||||
softer term) transition from the routine of school. However, both the company
|
||||
and the team have made it easy to adjust.
|
||||
Working abroad, with the additional COVID restrictions, is a harsh transition
|
||||
from the routine of school. However, both the company and the team have made it
|
||||
easy to adjust.
|
||||
|
||||
* The daily stand-up meeting, and weekly retrospective seem more important than
|
||||
ever when you can potentially not talk to your colleagues for days due to
|
||||
|
|
Loading…
Reference in a new issue