Being a software developer be prepared to accept your mistakes.

We cannot always be right. Even an expert developer can make a stupid mistake. In daily routine, we hear the words Test Driven Development, design principles to increase the code quality, reducing the bugs, but inside this article lets discuss the most critical work quality which we often miss while working in a team. How you react, when someone disagrees or found some flaws in your implementation.

I have been working in this industry from the last eight years, and apart from my working hours, I spent the time to improve my soft skills to be less wrong. However, there are occasions, when I go wrong by mean of code implementation or by skipping some use case. When it got caught, I start addressing it.

The craft you cannot acquire in a day, it takes time. Think of another person’s prospect, and let him make his claim also listen till the end.
Inside your brain change the statement I can’t be wrong to Anyone can be wrong at some time. The more you hold yourself to speak the cooler you will be in response. Aforementioned is the crucial skill which matters the most in building some great teams. You cannot just rely on your technical skills.

You can avoid bugs by following certain principles and methodologies in In software development, but you cannot always write bug-free code. It could be because of unclear requirements specified in spec documents or wrong acceptance criteria in a user story. It’s not the developer who is responsible, but you are the one who can avoid this at the time of implementation by thoroughly looking into specification and acceptance criteria, if anything doubtful, notify to other teammates and stakeholders.

You are not only responsible for writing code, but you are also the cornerstone of the whole development team. By being a little alert, you can take the project to a thriving mark.