If you are a programer, have you ever worked in a team ? Except you’re a freelancer and work alone. From the time we started programming util we got experiences, that has been a long time with a lots of faults.
Me too. I’ve made mistakes in programming for more than 6 years, and it never stop. Otherwise, the number of the mistakes I made, it is declining day by day. Of course, I’ve learned from mistakes. But I almost work in a team 😉 ? Better than me ? we have. Worse than me? we have. Didn’t know anything, yes, we have (or that guy was me when I joined the first team 😉 ). Assume you have an expert in your team, that’s great, there is one bright sign for a successful project. But…
Since We work in a team with teammates, beside the strategy and process of company can avoid a lot of mistake but can not do it all.
You see, expert can save him self or one or 2 more but can not do all. Like this
It could be terrible if a bad skilled guy join your team, how do you deal with that ? deny ? don’t assign any task for him ? Tell you boss to fire him ? With all my respect, don’t do that. You can do it one, two but can not do it all the time. Deal with it 😉 Send to every warm welcome, that’s the great way to do. But you need to do something more.
A team with not equal skills can be a team ? YES, I can say that to you and how we could deal with that.
I classify the mistakes need to be avoid here to some reasons :
– Project deadline is missed.
– Project deadline is missed and it looks awful
– Project deadline is missed, looks awful and doesn’t match with requirement
– Project deadline is missed, look awful and crash all the time
– Can not finish project
– Can not finish project and get fired ;).
Ok, that’s enough, don’t try to blame any one else, be a man, take the responsibility and exhort everyone to each other. But, of course we can do it better.
The most important thing to be an expert team is cover each others. By the way, we are not in Army, right ? Cover what ? Covering the teammates is also covering yourself. Assume that you have skilled and can avoid almost common mistake while programming, but are you sure all the team can do it, too ? Or you think you never make mistakes ? We are human. We’ve learn from the beginning and become expert after a long time.
In out team we created a coding rule and coding process to avoid misunderstanding requirement and our project can be consistent and easy to maintenance. We use Agile to manage tasks and project delivery time life to avoid missing deadline and it could be flexible to change target (requirements). To avoid missing requirement, we create a pull request after finish our task, so, anyone can review what’s changing and avoid conflicts or logic’s mistake. To avoid bad skilled code, we create a Shield, event that a bad guy unfortunately makes a programming mistake, it will work without any system fault. It gives you one change to fix it without any issue, that’s very important for user experience, they can continue using the app. Those stuffs come along with the learning spirit of the team, we’ve grown up day by day, together with out any bad case I listed above. Event the team will scale to be bigger in the feature, everything will be ok, the bad guys can self-learning to be come an expert, your team will have more expert that they will cover you (if you think you’re the expert ;)). Give a change, receive a better feature. Come together, come further.
Nam Nguyen
Lead iOS Developer
RingMD
https://ring.md