Skip to content

Instantly share code, notes, and snippets.

@bobbzorzen
Last active May 14, 2018 13:29
Show Gist options
  • Save bobbzorzen/8622006 to your computer and use it in GitHub Desktop.
Save bobbzorzen/8622006 to your computer and use it in GitHub Desktop.

6 simple techniques for getting 15 sentences of report text


  1. Write down the questions!

    Writing down the questions you're supposed to answer is a great way to increase the sentence count. there are usually 3-4 of them so if you write them down you're almost a third of the way there.

  2. Did you miss a semicolon somewhere?

    Any problems you encountered, big or small is a great way to increase the sentencecount. Did you forget to write a semicolon and get some sort of error message? Did you accidentally write a space before the PHP opening tag and get a headers already sent error? Well if you did congratulations you've got about enough to get to 15 sentences right there. Rejoice, grab a coke and play some games!

  3. Confused about something?

    Have you at any time during the assignment felt confused about what's happening? Or did you at any time during the assignment feel NOT confused? Then write down what you were or were not confused about. BOOM another 50 sentences right there whether you're a pro or newbie.

  4. Did you do something you felt proud about?

    If you've written some peice of code that you felt where challanging or just fun and you feel proud about it, write it down! Bobba loves to read about the proud students! It makes him proud of them! And if you're finding the subject entertaining it's eazier to write about.

  5. Do you have an opinion?

    Do you have an opinion about anything that happened in this assignment? Did you think it was great that you got to learn this thing or did you think it was completely useless? Or even if you didn't have any real thoughts about it you can just write that down. It's bound to give you at least a sentence or 2 :)

  6. Write an errorlog

    Whenever you encounter a problem of any kind, write down a word or 2 in an errorlog. Nevermind sentance structure or anything like that. Just write it down so you can look at it when writing your report texts. It's hard to remember the little things that went wrong once you've solved them.

    Author - MrIsaksson

Final words

  1. Remember that 15 is not the max! If you write even a sentence or 2 more it shows initiative and dedication. And those are good qualities.
  2. You can write about almost anything in the report texts. And the more you write the eazier it gets.
  3. Before you submit, put a newline at every dot/questionmark/exlamationmark and count the rows. 15 is the minimum and with these tips i hope you can all get there every time.

Remember kids; programing is fun, and so is writing about it ;P

@Limeliz
Copy link

Limeliz commented Jan 28, 2015

"where" -> "were" in the third one: Confused about something? (last sentence)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment