
My group had its first CG1413 programming meeting last Friday (120210).
What went well during the meeting?
Since my group had two C++ programmers with a commendable knowledge on programming, things went really smooth as we didn’t have to get stuck on any coding problems. As a result more time was available for planning and enhancing our design. Ideas flowed and we were able to complete the task swiftly. Personally it gave me an insight on how more experienced programmers think and I was able to pick up a few tips and tricks from them.
What went bad during the meeting?
Having two C++ programmers in our group seemed like a double edged sword to me. Though it helped speed up things, I felt that they were a little too quick for me. They always seemed two steps ahead of me in the way the think about the code and planning for it. As a result I wasn’t able to contribute much in terms of the program.
Initially for this meeting we were unable to find a suitable venue but with the help of one of our Teaching Assistants (Mr. Achudhan) we were able to find and book a proper meeting room.
My Role during the meeting:
I was tasked to prepare the agenda and take down minutes during the meeting.
Agenda:
The agenda was pretty easy to make as we had already discussed informally on what are the possible things that we need to address during the meeting pertaining to the project. Finding a template for the agenda was a problem at first but after scouring the internet for more than an hour I was able to find one.
Minutes:

In order not to forget what we had discussed, I took down the minutes as and when the points came across. When I took a look at the minutes the following day I was pretty surprised that we had actually discussed on so many points and some of them were even obscure to me. At that instant I knew how important minutes were in a meeting.