Internal meeting (Part 2)
The three attendees adopted different attitudes during the meeting. The project consultant was quite relaxed. He was sitting on the side and only interfered when something was not clear about the customer's needs or to tell an anecdote. The remainder of the time he was doodling on his smartphone. After all he does not know how to program so it is only understandable that his contribution to the meeting would not be as important. On the other hand, the junior coder seemed very nervous. His face looked bright red and he would hum at every silent moment, as if he attempted to calm himself. He accepted every correction of the senior coder without question since it was the first ever project in PL/SQL (a programming language) on which he had worked. The senior coder's attitude was the most normal, he was neither too relaxed nor nervous. He always communicated his corrections in a friendly way and did not try to belittle the junior coder. The two programmers were facing each other as they were the ones mainly talking during the meeting. Moreover, they were sitting right in front of the projector since they needed it to display the code and discuss it.
As a side note, the meeting ended up lasting longer than planned because they had misunderstood the purpose of our visit. They were supposed to conduct their meeting as if we were not there, but instead they kept on explaining nearly everything about the code to us. Strangely enough it was the most nervous person, the junior coder, who talked to us the most. None of us had the courage to interrupt their explanations, which is a pity since they ended up losing even more time for us. But we are still thankful for the extra knowledge we gained.
In conclusion, Siemens deals with meetings and group projects in a somewhat different way from our experience at college. The biggest difference is that no notes are taken during meetings and there is no hierarchy in group projects. Positions such as project consultant or programmer are the only quality that differentiates an employee from another.
Sorry it's very long :( Thank you!
다양한 영어 선생님을 검색해 보세요...
교정 · 2
1
Internal meeting (Part 2)
The three attendees adopted different attitudes during the meeting. The project consultant was quite relaxed. He was sitting on the sidelines and only interrupted when something was not clear about the customer's needs or to tell an anecdote. The remainder of the time he was using his smartphone. Of course, he does not know how to program so it is only understandable that his contribution to the meeting would not be as important. On the other hand, the junior coder seemed very nervous. His face was bright red and he would hum at every silent moment, as if attempting to calm himself. He accepted every correction of the senior coder without question since it was the first ever project in PL/SQL (a programming language) on which he had worked. The senior coder's attitude was the most neutral; he was neither too relaxed nor nervous. He always communicated his corrections in a friendly way and did not try to belittle the junior coder. The two programmers were facing each other as they were the ones mainly talking during the meeting. Moreover, they were sitting right in front of the projector since they needed it to display the code and discuss it.As a side note, the meeting ended up lasting longer than planned because they had misunderstood the purpose of our visit. They were supposed to conduct their meeting as if we were not there, but instead they kept on explaining nearly everything about the code to us. Strangely enough it was the most nervous person, the junior coder, who talked to us the most. None of us had the courage to interrupt their explanations, which is a pity since this ended up using up even more of our time. However, we are still thankful for the extra knowledge we gained.
In conclusion, Siemens deals with meetings and group projects in a somewhat different way compared to our experiences at college. The biggest difference is that no notes are taken during meetings and there is no obvious hierarchy in group projects. Positions such as project consultant or programmer are the only quality that differentiates an employee from another.
Sorry it's very long :( Thank you!
더 빨리 진행하고 싶나요?
이 학습 커뮤니티에 참여하고 무료로 연습해보세요!
집에서 편안하게 언어를 배울 수 있는 기회를 놓치지 마세요. 경험 많은 강사진을 살펴보고 지금 바로 첫 수업을 신청하세요!
오늘 학습 시작하기
