As a result, the gap between my translating sessions has increased which has just about removed any additional fluency in Racket I gained at the beginning. I found myself having to look up functions in the Racket docs that I had looked up before but because of a lack of practice did not get them committed to memory.
I also realised that my efforts were little more than translating Python idioms into Racket syntax. I would really need to know Racket much more deeply to replace the idiomatic Python with idiomatic Racket.
I've decided to halt my translation efforts for the moment. I may come back to it, I may not.
Through this process, I see that Racket is a very big language. Big in both breadth and depth. I believe that once a person has mastered Racket they could become very productive using it. I do suspect that probably involves building up personal libraries of functions for the domains in which you want to use Racket.
