Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Testing the waters, I'd played with the idea of a story with basically this setup:

Two new developers start at a company/startup, and are brought in to do a six-month sprint to fix a stalled/broken product after the development team becomes unavailable because reasons. So, they're dropped into a codebase and are trying to pull everything together.

However, as they work through into deeper and deeper parts of the system, the commit messages and comments get more and more cryptic and unsettling, hinting at the reasons for the prior team's dissolution, the business forces that caused that to happen, and maybe something worse/better going on outside.

I'm really lazy though. :(



>after the development team becomes unavailable because reasons.

Every member of the programming team was attacked and killed by wolves in unrelated incidents on the same night.

And they said it couldn't happen...


I like it. It reminds me of something like System Shock (2 is the one I played), where you learn about what happened on this ship before it was overrun by mutants from journals and such. Instead of a book, this may work well as a game of some sort. Perhaps even text-based?


This is a really good idea. Too bad I seriously suck at writing fiction or I'd pick this up.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: