Someone confronted me about Ideal vs Necessary Evil in regard to coding to best practices. Today there was a loud debate among myself and two other developers regarding how to handle some legacy code. One developer wants the the legacy code refactored and testable the other wanted to modify the code quickly since the company plans to rewrite the application after the next deployment in a month. I wanted to make a code branch of existing code then refactor as much as possible as long as the new functionality ......
Over all I think the best indication that someone will be a good agile team member is: Demonstrates a long-term desire to move from journeyman to craftsman. (study groups, software related blogging, seeks out training) Demonstrates that they will share knowledge insights with others.(mentoring,being mentored not just for newbies all team members) Open to debate and new ideas. (question whenever a quick solution does not follow solid principles, or adds unnecessary technical debt) Willingness to work ......
I am learning all I can about the solid principles. Currently I am reading about the Single Responsibility Principle (A class should have only one reason to change). If a class has more than one responsibility, the responsibilities become coupled. This kind of coupling leads to fragile designs that beak in unexpected ways when changed according to Bob Martin. An example I have seen lately is the case of the widget.com public site and the widget.com customer site having the exact same code base except ......