Quarterly test KasperskyLabs 148 B1/B2 2024/06/24 19:39:14 20240624_1939 Sergey Telelyukhin sergey.telelyukhin@gmail.com 57 inc_drills/grammar_participle_clauses_selection_b2_03_selection.csv 1 Grammar B2 - 03 Participles clauses 0 Attending Attended Having attended Having attended Having attended 1 1 Having being confused Confused Been confused Confused Confused 2 2 Realised Realising Having realised Having realised Realised 0 3 Ashamed Having been ashamed Ashaming Ashamed Having been ashamed 3 4 Produced Having produced Producing Produced Producing 0 60 inc_drills/grammar_adverbial_clauses_selection_b2_02.csv 2 Grammar B2 - 02 Adverbial clauses 0 in case provided unless provided in case 0 1 in case although but although although 1 2 provided as long as although as long as as long as 2 3 because in case if in case because 0 4 as long as unless if unless as long as 0 40 2 Grammar B2 - 02 Writing (~150 words x 2) When possible, use the following:
as
As a result of (+ noun phrase)
According to (+ noun phrase)
although (+ clause)
however
therefore
as a result (+ clause)
in order to (+ infinitive)
What's more
In addition
Taking into account (+ noun phrase)
What is important is that
]]> What strategies can you use to manage difficult negotiations?
  • If a situation is obviously urgent, do you always expect a quick response?
  • How can you avoid lengthy meetings?
  • Would you like to be the hero of the month at your company? What project ideas would you like to promote?
  • How do you convince people to do something for you?
  • When is being transparent a good choice in business?
  • What does the triple bottom line take into account that wasn't included before?
  • Are working conditions the only ethical concerns of employees in your country?
  • Would you buy some particular brand of clothes to show your professional status & success (e.g. a suit by Armani)? Or would you be ready to buy clothes only because they were ethically produced?
  • Do you avoid fast fashion brands?
  • Have you ever lacked time & resources for prototyping that led to a technical debt? How did you deal with it?
    • ]]>     (more) effective. If you can rescue save | spare time from unnecessary meetings you (can then) invest this time into your project, into your work. So the art of avoiding these kinds of meetings can be very important for your career and personal efficiency. A lengthy meeting usually happens when participants don't follow a strong agenda, when nobody gives a is given the role of meeting's facilitator, when an the agenda is huge, a lot of people are invented invited to the meeting, when people aren't limited with a time a for their speech or when all of explained reasons happen together. According to the reasons above a very effective way to make meetings shorter and effective are is following the next steps of 'an ideal meeting': Firstly you need to create an agenda which can be discussed with a minimum of participants. Sometimes a long agenda can be spliced to into several ones. Secondly each meeting should have a facilitator - a person who watches on time and on the agenda and has a power to shut up everybody. In conclusion I can say that these simple principles can make lengthy meetings much more effective and shorter. ===== If a situation is obviously urgent, do you always expect a quick response? === Unfortunately usually a situation which is obviously urgent for one person can't be recognized in the same way by another one. So if you are a person who recognize recognises an urgency you sometimes spend a lot time to connect to the reliable (right | relevant?) person and in order to explain the situation. Although there are a lot of obviously urgent situations for everybody such as a car accident or when a house is in on a fire. In these cases people usually response respond quickly except in cases when a shock stops them. Additionally you can be in a place when nobody is near and you can rely only on yourself. So In conclusion I think that the a better strategy in urgent situations is relying on yourself and do not expect not expecting a quick response. ]]> 70