feat: Allow viewing the code from result or history screens

[sashalex007]

Fantastic project. Would it make more sense to start the timer on the first keystroke?

https://github.com/unhappychoice/gittype/compare/main...sashalex007:gittype:feature/start-timer-on-first-keystroke?diff=unified&w

[linear]

E-667

[unhappychoice]

Thank you for your interest in the project and for the suggestion!

After careful consideration, I've decided not to implement this change. The countdown ("3, 2, 1, GO") is an intentional design choice that serves a specific purpose in the game experience.

While I understand that typing tests like Monkeytype start the timer on the first keystroke, gittype is designed as a game rather than a pure typing speed measurement tool. The reaction time to the "GO" signal is part of the intended gameplay mechanics, adding an element of readiness and anticipation.

The current behavior aligns with the game's design philosophy, so I'll be closing this issue. I appreciate your contribution and hope you continue to enjoy using gittype!

[sashalex007]

Thanks for your consideration!

The main reason I prefer starting the timer on the first keystroke is because it gives me the ability to glance over the code before I start to fully understand and absorb the logic. This is somewhat tricky for me to do on the fly while I'm concentrating on the typing- especially for longer challenges.

In principle, this "glance over" period could be moved to the end of the challenge to stay consistent with game mechanics. Would you be open to that?

[unhappychoice]

That’s a fair point. Having a way to review the code before or after typing could indeed be useful.
It might make sense to let players look back at the code from the result or history view once the challenge is finished.
It’s not a simple change to implement cleanly, but I like the idea as a possible feature direction. Thanks for the thoughtful suggestion.