I had a thought about anthropomorphizing the compiler into a role much like a fairy in Zelda or Spren in Stormlight Archives.
I'm not committed to this path, but it is something I want to consider and explore.
I like the notion of having the compiler as your traveling companion that is helping your do your job. It would have the role of taking your channeling and turning it into something in the real world.
One thing I like about this is that it turns the compiler into an ally rather than an enemy.
I can also imagine having the compiler as a traveling companion be useful in other ways, similar to the fairy companions in Zelda, where they can potentially tell you where to go next or how to defeat certain enemies. For example, the "hints" that are in the book could be turned into advice from such a traveling companion.
I like that it adds a bit of richness to the world, and that all programmers could have their own traveling companion.
Let's talk names. Two names are associated with the compiler in C#: Ryu, as in RyuJIT and Roslyn. I don't love either of those names for this character. But Ryu means "dragon" in Japanese, and can also mean "Flow". It is some hoop jumping, but I kind of like the name Flow for your companion.
Another benefit of a traveling companion is that they can elaborate on some of the world's lore without needing a specific human traveling companion there.
It's a small cost to explain Flow upfront to have room for something that can point you in the right direction as needed, and explain the world a bit more.
I had a thought about anthropomorphizing the compiler into a role much like a fairy in Zelda or Spren in Stormlight Archives.
I'm not committed to this path, but it is something I want to consider and explore.
I like the notion of having the compiler as your traveling companion that is helping your do your job. It would have the role of taking your channeling and turning it into something in the real world.
One thing I like about this is that it turns the compiler into an ally rather than an enemy.
I can also imagine having the compiler as a traveling companion be useful in other ways, similar to the fairy companions in Zelda, where they can potentially tell you where to go next or how to defeat certain enemies. For example, the "hints" that are in the book could be turned into advice from such a traveling companion.
I like that it adds a bit of richness to the world, and that all programmers could have their own traveling companion.
Let's talk names. Two names are associated with the compiler in C#: Ryu, as in RyuJIT and Roslyn. I don't love either of those names for this character. But Ryu means "dragon" in Japanese, and can also mean "Flow". It is some hoop jumping, but I kind of like the name Flow for your companion.
Another benefit of a traveling companion is that they can elaborate on some of the world's lore without needing a specific human traveling companion there.
It's a small cost to explain Flow upfront to have room for something that can point you in the right direction as needed, and explain the world a bit more.