This is another collection from recent meetings and trips. It works best if you can find a native English speaker with exposure to corporate America to elaborate on the finer points that I cannot cover well here.
* I'll ask the questions first. Please feel free to chime in. [I''ll ask the questions first. Please feel free to add yours.]
* If we have to jump through hoops to get there, we have a bad design at the outset. [If we have to do through extraordinary steps to get there, we have a bad design to begin with.]
* It is a totally bogus question. Why do you have to ask what the system is like? [It is a totally nonsense question. Why do you have to ask what the system is like?]
* This one-stop shopping will be convenient for the customers. [This one single contract point will be convenient for the customers.]
* We got twenty minutes to the top of the hour. We should be able to complete this review. [we have twenty minutes to the end of the hour. We should be able to complete this review.]
* I like to get your usage model in order to talk to my engineers. [I like to know how you use this in order to talk to my engineers.]
* Let me call you right after this concall to get to the nitty-gritty of this requirement. [Let me call you right after this conference call to get the details of this requirement.]
* Another option is to tinker with the new hardware to get a feel of it. [Another option is to play with the new hardware to get a feel of it.]
* Enough doom and gloom for this difficult technical issue, let's move on to the next topic. [We have discussed enough on the down side of this difficult technical issue, let's move on to the next topic.]
* Going forward, the intention is to maintain this transparency so that customized code can be removed. [From now on, the intention is to maintain this compatibility so that customized code can be removed.]
* We will not comment on this news; this is the party line. [We will not comment on this news; this is the the official stance.]
* That is Ninja programming to me; you have to know what you are doing. [That is really some programming to me; you have to know what you are doing.]
* You have the pen, you have the control for the project. [You are the one writing the requirement document, you have the control for the project.]
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment