Read the following context and answer the question. Context: I have always been a "handyman" involved in various building projects around the house. One particular time I was refinishing a section of ceiling. I had laid in the wiring and insulation by myself and all that remained was nailing a number of heavy 4ftx8ft gypsum wallboard panels onto the rafters of the 8 ft ceiling. I had arranged for a paid assistant to help me since the height of the ceiling and the weight of the wallboard was more than I could handle. When the time came, the assistant didn't show up and did not even call. I was pissed as hell. After my messages were not returned, I had what can only be called a "rage" of determination. Using a six foot ladder, three 2x4s and my head(literally) I hefted the heavy wallboard, Using leverage I placed them one by one on the overhead rafters, held and braced them with my head, glued and nailed them there all by myself. About a half hour after I finished, I was standing there smugly trying to figure how I did it so easily when there was a knock at the door. Of course it was the assistant with a lot of excuses. He seemed surprised when I told him I was finished. He looked up at the ceiling and said "how in the world did you get those up there by yourself?" I said, "Oh, believe me, You helped more than you will ever know!" I learned a lot from that. Anger has its place in your life. You have to control it and use it directly to solve a problem. To this day I do not know how I accomplished what I did the way I did it. But, if I hadn't been so angry I would never have attempted it at all. Life is full of little lessons. Pay attention to them and learn. If you have to lash out, lash at solving the situation you are in instead the person who caused it. It is significantly more productive that way. Question: After the end of the story, how does the handyman probably feel about the assistant? Answer:
OPTIONS:
- Grateful
- Angry
- not enough information
- Annoyed

Answer: Grateful

Read the following context and answer the question. Context: There was a boy named Chan who loved his parents, though they did not love him back; he was not even given a first name. He had been born in the wrong month, during the wrong phase of the moon, his parents told him, and had brought them nothing but bad luck. The promotion at the factory promised to his father was taken away at the last moment. The garden his mother worked in nearly every day never produced anything more than the most meager of weeds since Chan's birth. It was often sunny in the little Chinese village, but there was an almost constant gloom over their house, as if a rogue cloud were blocking the sun only over their property. And his parents, of course, blamed Chan for everything. He was small for his age, and usually quiet. He liked to listen to people instead of talking, filling himself with stories. He was a good boy and always did as he was told, and could see the good in his parents, even if others couldn't. Every so often, his mother would allow him a sweet, or his father would bring home an origami folding kit. They didn't like to show it to others, but his parents could be kind. Chan was patient and knew they would love him eventually. He was digging one day between the fence and the west side of the house for grubs to feed to his pet chameleon, Rainbow. It was a warm July day not long after his tenth birthday. He often went there because it was cool and damp from the shade of the trees, and the worms seemed to like it there. He never took more than he needed, then he thanked the grubs for sacrificing their lives so that Rainbow could remain living and being his pet. Chan was very kind-hearted when it came to grubs. Question: How did Chan feel about grubs? Answer:
OPTIONS:
- kind-hearted
- not enough information
- disgusted
- cold-hearted

Answer: kind-hearted

Read the following context and answer the question. Context: One of the challenges that every community faces, particularly teams inside a larger community, is the ability to coordinate what goals and ambitions the team is going to work on. Traditionally this has always been somewhat ad-hoc: people join a team and work on whatever they feel like. Ideas are ten-a-penny though. For most teams that work on larger projects (such as events, software, products and more) to actually be productive, coordinating this work can be complex: some projects require coordination across many people with different skill-sets, time-availability and resources. Something I would like us to work towards in the Ubuntu community is encouraging a culture of best-practise in how we plan our work and coordinate our awesome teams to work together on projects. I believe this kind of coordination can help our teams increase the opportunity for success in their work, feel more empowered and productive and provide greater insight to people outside those teams on what the team is doing. An effective way of doing this is to build a Roadmap for each cycle. This provides an opportunity to capture a set of goals the team will work together to achieve in each six-month period. This article outlines how to build such a Roadmap. While at first a roadmap can feel a little like a nod to the gods of bureaucracy, they actually possess many benefits: * Direction one of the biggest complaints teams often report is a lack of direction. If a team gets into the habit of creating a roadmap at the beginning of a cycle, it gives the team a sense of focus and direction for the coming cycle. * Documented commitments are more effective a common rule in Project Management training is that actions assigned to people in a shared document are more effective than ad-hoc or private commitments. By documenting who will work on what in a cycle and putting their name next to an action can help seal a sense of accountability for their contributions to the project. * Feeling of success regularly revisiting a roadmap and... Question: How many teams are there? Answer:
OPTIONS:
- 5
- not enough information
- 8
- 104

Answer:
not enough information