Modern testing for modern stacks

As I was reading this blog I remembered many of my ex-colleagues and developers. I wish I would have this link earlier so that I could have shared it with some of them. It's hard to find an environment where all people believe in this principle. Some people don't like accepting mistakes, some people treat people who know less with less respect. A good developer or tester should always be open to feedback and try to help others. You shouldn't take feedback personally. Treat people who know less than you with respect, deference, and patience as only true authority stems from knowledge, not from a position. I especially liked the 10th point "Critique code instead of people û be kind to the coder, not to the code. As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc."

I can say that ego-less programming is also one way of programming style to improve the quality. Once we start the programming we should accept or familiar with getting mistakes. Once we get a mistake we shouldn't stumbled on seeing the error.We have to find the root cause and correct it. May be that is the last step failure in our program before succeed it. It's no wonder that everyone will feel bad when others find errors in the code. Sometimes our code is not accepted or if it contains bugs don't feel embrace and use the first method and keep going. The core principle is to leave the code in better condition than before you were there. Being open and inclusive is the best way to allow this developer to get in the groove of things and become productive. We should study and improve our skill sets since languages are being developed by the user ie we should have a mind that change is the only constant word.

Such a nice article that I wished these were part of the culture. I can relate to each of the points through my career experience. Its a very well written article. I can also relate to my experience with clients too. I agree to all the commandments, should follow them.

I agree with all the commandments quoted but those that stood out for me was - Understand and accept that you will make mistakes: I remember when i started I spent too much time on coding hoping that this reduces the time that was spent on code review but this only increased the time that I took to code until I realized that mistakes are going to happen and that is the sole purpose of code review,No matter how much "karate" you know, someone else will always know more: learning is never bad, you don't have to feel bad about asking people for help,Don't rewrite code without consultation: this was something I debated once. Reusing code is something that to take pride on as a coder but there are time when you have to make a trade-off to make your code more understandable. Your code may last longer in an organization than you do hence it is vital that you code having in mind you will not be there every time to explain your code.

It is a good read and I pretty much agree with most of the commandments listed out. It emphasizes on minimizing personal factors to improve quality.I feel the point "Understand and accept that you will make mistakes" will hold good only if we reach out to learn from the mistakes else it would cost you a great deal.Overall its good to inculcate these commandments at QXF2 and try to follow the same.