Feanor
Karazhan Raider
- 7,766
- 35,304
Cr8sswareT
The not too distant future (in this case 100 years from now)
A programmer for a company namedcloakbecomes obsessed with using their beta machine. The machine goes back and forth in time. The company is very small, working day and night. They are working on patenting their technology before other competitors in the emerging industry.
The graveyard shift programmer begins using his crossware build to revisit the past. He made the thing. Named it. Without him there is nocloak. He goes over several events before focusing on his own past. The middle of the story deals with the programmer visiting the same event several times, experimenting with the outcome. The present changes throughout the story, but unforeseen effects are also recorded. The past changes as well. The concept of time is mutable.
The end is anticlimactic (or is it?), as the owner ofcloakrightly decides to fire the programmer before he can finish.
The not too distant future (in this case 100 years from now)
A programmer for a company namedcloakbecomes obsessed with using their beta machine. The machine goes back and forth in time. The company is very small, working day and night. They are working on patenting their technology before other competitors in the emerging industry.
The graveyard shift programmer begins using his crossware build to revisit the past. He made the thing. Named it. Without him there is nocloak. He goes over several events before focusing on his own past. The middle of the story deals with the programmer visiting the same event several times, experimenting with the outcome. The present changes throughout the story, but unforeseen effects are also recorded. The past changes as well. The concept of time is mutable.
The end is anticlimactic (or is it?), as the owner ofcloakrightly decides to fire the programmer before he can finish.