The Two Stories(三)

2019-03-02 23:43|来源: 网路

The First Story:

    On August 26, 1999, New York City was struck by a terrible rainstorm. The rain caused the streets to flood and the subway system almost came to a stop.

    Unfortunately, this happened during the morning rush hour. Many people who were going to work were forced to go home. Some battled to call a taxi or to get on a bus. Still others faced the storm barvely, walking miles to get to work.

    I happened to be one of the people on the way to work that morning. I went from subway line to subway line only to find that most service had stopped. After making my way through croweds of people, I finally found a subway line that was operating. Unfortunately, there were so many people waiting to board the subway that I could not even get down the stairs to the platform. So I took the train going in the opposite direction, and then switch back to the downwindow train. Finally, after what seemed like forever, the train reached my stop. Then I had to walk several blocks in the increasingly heavy rain. When I finally got to my office, I was wet through, exhausted and discouraged.

    My co-workers and I spent most of the day drying off. When it was 5:00 p.m, I was ready to go home. I was about to turn off my computer when I received an e-mail from Garth, my Director:

    I would like to thak all of you who made the effort and eventually reported to work. It is always reassuring, at times like these, when employees so clearly show their devotion to their jobs. Thank you.

    Garth's e-mail was short, but I learned more from that brief message than I ever did from a textbook. The e-mail taught me that a few words of appreciation can make a big difference. The rainstorm and the traffic troubles had made me tired and upset. But Garth's words immediately refreshed me and put a smile back on my face.

 

The Second Story:

     I was a single parent of four small children, working at a low-paid job. Money was always tight, but we had a roof over our heads, food on the table, clothes on our backes, and if not a lot, always enough. Not knowing we were poor, my kids just thought I was strict. I've always been glad about that.

     It was Christmas time, and altough there wasn't money for a lot of gifts, we planned to celebrate with a family party. But the big excitement for the kids was the fun of Christmas shopping.

     They planned weeks ahead of time, asking each other what they wanted for Christmas. Fortunatly, I had saved $120 for presents to share by all five of us.

     The big day arrived. I gave each kid a twenty-dollar bill and reminded them to look for gifts of about four dollars each. Then everyone scattered. We had two hours to shop; then we would meet back at the "Sanata's Workshop".

     Driving home, everyone was in high Christmas spirits, except my younger daughter, Ginger, who was unusually quiet. She had only small, flat bag with a few candies-fifty-cent candies! I was so angry, but I didn't say anything untill we got home. I called her into my bedroom and closed the door, rady to be angry again. This is what she told me.

     "I was looking around thinking of what to buy, and I stopped to read the little cards on the Giving Trees." One was for a little girl, four years old, and all she wanted for Christmas was a doll. So I took the card off the tree and bought the doll for her. We have so much and she doesn't have anything.

      I never felt so rich as I did that day.

 


转自:http://www.cnblogs.com/SanMaoSpace/archive/2011/11/26/2264655

相关问答

更多
  • jbehave-to-gherkin项目可用于将故事导出为小黄瓜格式。 之后,可以使用泡菜处理小黄瓜功能,以创建一些非常好的html输出。 The jbehave-to-gherkin project can be used to export stories to gherkin format. After that, the gherkin features can be processed with pickles to create some really nice html output.
  • 基本上,我尝试将用户故事的大小保持在1到10个工作日内完成。 这使我无法将Mike Cohn所说的“Epics”或“Themes”作为用户故事传递给开发人员,另一方面阻止我的用户故事如此具体以至于暗示解决方案(他们应该描述问题,而不是应该如何解决)。 就内容而言,我确信我的故事仅包含商业价值 - 它从未描述我如何满足需求,也不需要“非用户领域知识”来理解。 很好的例子:作为一名内容管理员,我希望所有用户都必须先登录才能开始回话,以便拒绝他们发送垃圾邮件的能力。 不好的例子:将验证码添加到网站。 另一方面,任 ...
  • 好。 经过一番搜索后,我发现这个问题在JBehave 3.8中得到了解决。 JIRA链接: http : //jira.codehaus.org/browse/JBEHAVE-841 我更新到最新的jbehave版本,这工作正常。 OK. After some searching around I managed to find that this issue was fixed in JBehave 3.8. JIRA link: http://jira.codehaus.org/browse/JBEHA ...
  • 您需要使用witadmin.exe导出Team Project的流程配置文件 导入和导出过程配置[witadmin] witadmin exportprocessconfig /collection:http://TFS2013:8080/tfs/defaultcollection /p:MyProject /f:C:\Temp\processconfiguration.xml 在需求类别中添加新状态,例如,“进行中”状态
    目前,您无法通过API过滤此内容,需要在客户端进行过滤。 我们正在研究一种新的,更强大的查询功能,但是a)这仍然处于设计阶段的早期阶段,并且b)它可能首先要完成任务。 一般来说,我们优先考虑目前无法通过API完成的事情,而不是可以完成的事情,但需要在客户端进行一些工作。 如果有人想要搜索整个工作区以查找与给定查询匹配的任务,那么这是您根本无法通过API实际执行的操作,因此我们会将其视为比这样的优先级更高的优先级,在此处过滤相对容易只有客户评论。 这并不是说我们不关心这些功能,而是我们想要做到这一切,但我们一 ...
  • 构造函数应该是__init__但您将其命名为__int__ 这可能是原因。 一探究竟 The constructor should be __init__ but you named it as __int__ That might be the cause. Check it out
  • 史诗的概念是,它是一个非常大的用户故事,需要打破 。 在Scrum中,积压是一个及时完善的过程。 我们从粗粒度的想法开始,随着我们越来越接近开始研究某些东西,我们得到了更好更好的形状。 用故事做这一切是很有可能的。 但是,许多团队发现,积压项目的定义不如故事更有用。 因此使用史诗。 例如,我几年前与我合作的一个团队被要求研究医学证据产品。 他们意识到所需的工作分为四大领域(即真正的大故事)。 有一个明确的优先次序,这意味着他们需要立即在其中一个领域工作,其他人可以继续。 该团队决定立即将第一个工作区域分解为 ...
  • @MrWiggles 正如t0rx告诉你很幸运有QA来编写故事/场景。 提出你的问题: 行为驱动开发鼓励您通过以文本格式表达所需行为的场景来开始定义故事。 您可以通过在Maven(pom.xml)中配置来运行JBehave Stories。 您可以创建一个文件夹,用于在包结构中存储您的故事文件,如下所示: Your_Project | | |--Source_Code | |--Stories | |--Testing ...
  • 在Rally中,只有缺陷可以转换为用户故事:不可能进行其他工作项类型转换。 In Rally only defects can be converted to user stories: no other work item type conversion is possible.
  • 检查浏览器中的控制台,很可能是javascript错误导致jquery_ujs无法拦截click事件。 jquery_ujs使用data-method属性侦听链接上的click事件,并创建一个表单并将其发布到服务器。 这个表单包含一个隐藏的_method输入,Rack接收该输入并在将请求传递给Rails之前更改请求的HTTP方法。 如果你有一个语法错误或引用错误阻止jquery_ujs运行,点击链接将发出一个GET请求,就像互联网上的任何其他链接一样。 所有这一切都是因为浏览器只会在您单击链接和POST / ...