Back to collectionTwenty Pages of Nitro Notes, Questions Still to Test
On the last day of the holiday, A-Zhen, an engineer on the chain research team, was working through the technical choices. She kept reading the Arbitrum Nitro source code and filled 20 pages of notes. The 20 pages gave the group something more precise than a general technology preference to discuss, while reminding them that reading code was not the same as testing it in operation.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
On the last day of the holiday, A-Zhen, an engineer on the chain research team, was working through the technical choices. With the project's direction taking shape, she needed to find out which parts of Arbitrum Nitro could support game needs and which possibilities were still assumptions.
She kept reading the Arbitrum Nitro source code and filled 20 pages of notes. Where the code left her uncertain, she separated behavior she could confirm from questions she still needed to ask rather than rush to a conclusion for the team. As work was about to resume, she selected several doubts related to game interactions to bring back to the group.
The 20 pages gave the group something more precise than a general technology preference to discuss, while reminding them that reading code was not the same as testing it in operation. A-Zhen's next step was to review the doubts with colleagues and decide which ones merited a hands-on trial in a development environment.