Communication and Bug Reports - Be Calm

 ·  4 min read
Communication and Bug Reports - Be Calm

As a software engineer intern at FULLSPEED TECHNOLOGIES INC, I have had the opportunity to learn about the company’s background. During my first week at the company, I had a virtual meeting with one of the admins for social media specialists. In this meeting, I learned about the company’s background in software consulting, digital marketing, and offshore development.

Effective Communication

In the following topic, I was able to know the organizational structure of the company and its mission and its vision. At FULLSPEED at end of every month, the company has a monthly knowledge sharing in which employees can share their knowledge with the team. During this time I was invited to another meeting for the introduction to the team/department that I will belong (Ronin department). The Ronin department is one of the development departments in the company.

In this particular virtual meeting, we talk about the department goals which are :

  • Project delivery
  • Productivity
  • Quality

Have you noticed that these three goals are not being numbered/ordered? in the department goals these three goals are treated as equal while the focus of the Ronin department core values is: 

  • Trust and Respect
  • Teamwork
  • Accountability
  • Professionalism

In the coming days, we are assigned different readings regarding effective communication, correctly asking a question, and effective debugging. An effective way of communication was the first thing that we need to work on during the first week of my internship this topic it’s talking about the different means of effective communication such as :

  • Be professional
  • Be prepared
  • Be confident
  • Be visual
  • Be mindful

How to Report a Bug

The next reading I had was about how to ask good questions and report a bug. in the first reading, I was able to learn different things that are crucial in software development, and asking a question in general the article focuses on the way how you should smartly ask a question and be able to consider the following things that you need to do before asking the question these are:

  1. Try to find an answer by searching the archives of the forum or mailing list you plan to post to.
  2. Try to find an answer by searching the Web.
  3. Try to find an answer by reading the manual.
  4. Try to find an answer by reading a FAQ.
  5. Try to find an answer by inspection or experimentation.
  6. Try to find an answer by asking a skilled friend.
  7. If you’re a programmer, try to find an answer by reading the source code.

Lastly

As mentioned above, you need to do those things first Before asking a technical question by e-mail, in a newsgroup, or on a website chat board, it is important to consider which forum you will be posting/asking your question.

Last week, we were assigned to read about how to effectively report a bug. Through this reading, I learned the importance of documenting and detailing a bug when it is encountered. By providing thorough information about the bug, programmers and developers can reproduce the issue and work on a solution. It is also important for users to remain calm and collected when a bug occurs. Taking a moment to pause and calm down can help to ensure that the bug is reported clearly and accurately.

Author

Jerson Dayuday