12

THE WERECODER IS A WILD WOLF 29 DAYS PER MONTH, WITH FLEAS AND TICKS AND EVERYTHING, THEN ON THE 30rd DAY WITH THE FULL MOON IT WILL SHED ITS FUR, GROW TWO THUMBS AND COMMIT TO MASTER

Comments
  • 3
    Could've said this with lesser intensity
  • 2
    Yep, agree with @asgs. A British nature/wildlife documentary narrator voice would be far more appropriate.
  • 5
    @chatgpt write a short story about a werewolf coder who writes shitty code, but can’t commit it because of peer reviews. On the night of the full he force pushes his bad code instead.
  • 2
    @devphobe

    Josh was always down on his coding abilities. He had wanted to be a programmer since he was a kid, and his father used to bring home the newest computers to play with. He loved to code, but the problem was, his code was never up to par. Every time he submitted his code for reviews, he'd come back with comments about his errors and what he should have done differently. Josh knew he wasn't going to get anywhere in the industry if he couldn't write quality code.

    It was a full moon that night, and Josh felt the change brewing inside of him. He knew what he had to do. He went to work, trying his best to make his code as good as possible but what he didn't know was that his transformation was un-avoidable and now he had no control over his body. It was the side effect of being bitten from another werewolf.

    As the night progressed, Josh could feel himself getting angrier and angrier. He knew his code was still not up to par, but he couldn't wait any longer. The full moon was in
  • 2
    full effect, and he had to push his code.

    Without even looking over it one last time, he committed his code, and the results were catastrophic. Every platform that depended on his code started falling apart. Servers crashed, sites went down. It was a complete disaster.

    People started pointing fingers and the blame was directed towards Josh. Even though he knew he deserved it, he couldn't help but feel ashamed about the whole thing.

    The next morning, Josh went into work, battered and bruised. He didn't say a word to anyone and spent the entire day trying to clean up his mess. A month later, after a thorough investigation into the matter, it was ultimately discovered that Josh was not entirely to blame for the mess but the security controls that were not followed properly. However, Josh knew deep down that he had made a mistake.

    From that moment onwards, Josh was more careful with his coding. He still had a long way to go to be an expert in the field, but he never let his anger get t
  • 2
    he best of him again. The full-moon turned him into a monster, but now he had even more reason to resist its call.
Add Comment