Ask HN:Review my science fiction story.

it should be formatted to be easier to read.

It's very difficult to critique specifics without handing you back a physical paper with redlines on it. Generally, the grammar needs a lot of work, as does the tense (jumping back and forth between past and present), and the flow from paragraph to paragraph. A lot of sentences are actually sentence fragments, and a lot of times I feel like you're instant messaging me your thoughts rather than writing a story about them.

The content itself is entirely vague as well. Sentences such as "OK if you eliminate the fact that he was a researcher of math at the age of 25, but what do you know, he was actually _the_ math genius." just confuse me and make it difficult to read. Saying "OK" as if I just called you out on something just does not seem right for anything except dialog (OK, maybe not all the time, but pick your places).

Saying "It wasn't just numbers, same was true for logic, innovation, ability to ask the awkward question, and then solving the hell out of them." is such an awkward way of introducing someone. You're building this person up so much in such a short amount of time, I have a hard time believing any of it (it's not true, but you need to be able to suspend disbelief). I've always learned that you should never ever ever tell your reader an opinion about something... that's "meta-story". Let your reader determine that he is a super genius if that's what he is, but don't tell them all these super-human things he can do... it sounds like a kid describing his action heroes. What you need to do is build up the character's credibility as the story flows, not wind up the character like a toy and let him run through the story.

The first few paragraphs of the story really need to pull a reader in to make them want to read more, and what I see in the first few is "another story about the future". I don't really see a character at first, and that's a big minus to me. I don't really want to read about a list of things that are true in your future, I want to read about the people in that future, and let the way they interact with their world describe what the world is like.

"He used a lisp program for all this stuff.He had read in school that it was one of the most oldest languages around but never belived that,it had the most advanced features." -- This contains detail that is not really pertinent to the story... not sure why it's really in there. In stark contrast to that specific technical detail, it seems odd that among all the other "future-y" stuff, it still takes long enough to collate some Google search results into a database that he is able to read a book (about more things that are too technically detailed).

Adding to this... "By this time the database was over with indexing and he was presented with a nice command prompt on his DataBaseLinux machine." is like saying "he raced to his car and drove to the store. his car was blue. he was sad to discover that the store was closed, however, so he could not buy the Sony 42" LCD TV with support for Dolby 5.1 surround sound built in that he was looking for". The key here is not that detail is bad, but you need to be consistent, and it has to be relevant detail. You need to expand on the parts that make the story human, and really cut down on the parts that make it technical.

Stylistically, I personally would not go into a story attempting to point out "this is like this in the future!" every chance I got. Specifically, it seems irrelevant that DRM is not an issue in the future, and it would confuse the hell out of a reader that was not familiar with the subject.

More comments to come likely, as I get some time to dig deeper.

EDIT: Sorry... if this is indeed a language barrier issue, that would explain a lot about the style comments I had. I then agree with khafra's comment. Otherwise there is a lot to discuss here. However, sentences such as "He didn't really thought about robots , but he did knew that his secretary robot was a good talk." makes me think the former is the case.

I read the first two sentences, wasn't drawn in, and would have closed the page, had this not been explicitly a request for help.

In short, what you wrote reads like notes for a story, not a story itself. Don't tell people it was 3065, and then give 3 word descriptions of other aspects of society. Instead, write out events that take are taking place that will lead people to understand these facts. Let the events pull people in, and when they are done reading, they will understand your setting. Once you've done that, the rest of the story should flow in a similar way.

So, the story has some potential. I would like to see what comes next.

However, you are severely limiting your audience in many ways. Most people don't know what it means to index a database. Many don't know what lisp is, or even what a programming language is (even worse that you call it a language and not a programming language). Etc... Ask someone who has never written a line of code and is afraid of computers to read this and they will come back confused.

Also, at the end, the character doesn't mean much to me. By this point I should feel the characters's passion for the question. I need to want the answer as much as he does. Giving him the feeling that its important to find out and conveying that will help a lot.

My guess is that something will be "undone" and thats the point of the story. If so, you have a neat idea here, but you need to keep the reader engaged. Take out technical details, flesh out the character, make me care about him and the world around him (whats good about it, whats bad about it) etc...

FYI - I don't mean to fully disparage your idea here. I think if you re-wrote it with the suggestions people here have given, it can be really good.

Also - nice idea having HN review a story. Its a nice change of pace.

As far as technical details in fiction are concerned, I think they can enhance a story when they are described in a way that lets non-technical users image a system that at least has roughly the right inputs and outputs. I find that Charles Stross does this very well, particularly in Accelerando, Atrocity Archives, and Jennifer Morgue.

From Atrocity Archives: "he'll have to enlist GCHQ and a scanning tunneling microscope to find it under all the 0xDEADBEEF spammed across the hard disk platters."

Even without fully knowing about these concepts, you still get a rich picture of of a hard-drive wipe (hopefully the reader is savvy enough not to imagine anything too bovine).

What this pretty much boils down to is the popular fiction writing mantra "show, don't tell".