Why Attend Meetings when Some Coding can be Done

I am sure many of us at some point of time in our career come across this argument from meeting attendees, primarily inexperienced guys, that he/she is very busy with his current tasks related with coding or testing, and that he may not be able to join the same given the fact that he agreed to attend the meeting earlier. Another instance that I have come across in relation with meeting is people coming up with laptops and get themselves busy with their tasks (coding/testing/others) while meeting is proceeding.


Thinking about my coding/testing while meeting is on!


Let’s try and understand what can be some of the different kind of meetings for an application programmer, or tester.

  1. Training
  2. Requirement analysis
  3. Architecture & design discussions
  4. Project status updates (SCRUM style etc)
  5. Awareness-related
  6. General get-together around team building

Let’s try and understand why meeting is called in the first place, and why can’t we just live without meetings:

  1. Achieve one or more objectives: Every meeting is called upon to achieve one or more objectives that the meeting initiator has. These objectives may be related with one or more of the following:
    • Obtain data points from different stakeholders
    • Know opinions from different stakeholders
    • Demonstrate and know feedback from different stakeholders
  2. Inform key stakeholders on progress
  3. Discuss and agree on different perspectives including milestones, deliverable etc.

So, why must an application programmer/tester attend those meetings if he/she has been invited, and what must he do in those meetings:

  1. Listen to those meeting proceedings attentively.
  2. Go mostly with notepad. Take your laptop only if you want to note the meeting minutes.
  3. Ask questions and get clarified as much as you can.
  4. Try and contribute to those meetings as your comments are very valuable. This is why you have been invited.
  5. Take notes of all those areas that is related with you or your team, and may impact your deliverable.

And, if you are not able to attend those meetings, decline politely along with reasons, if possible. In some cases, I found developers/testers not sending RSVP and meeting getting cancelled in last minute due to lack of quorum.

Ajitesh Kumar
Follow me

Ajitesh Kumar

I have been recently working in the area of Data analytics including Data Science and Machine Learning / Deep Learning. I am also passionate about different technologies including programming languages such as Java/JEE, Javascript, Python, R, Julia, etc, and technologies such as Blockchain, mobile computing, cloud-native technologies, application security, cloud computing platforms, big data, etc. For latest updates and blogs, follow us on Twitter. I would love to connect with you on Linkedin. Check out my latest book titled as First Principles Thinking: Building winning products using first principles thinking. Check out my other blog, Revive-n-Thrive.com
Posted in Software Engg. Tagged with .

Leave a Reply

Your email address will not be published. Required fields are marked *