Posts Tagged ‘ developer ’

Resume of the Practices of an Agile developer – part 2

Chapter two of this books also emphasizes the importance of being positive for every idea, because negativity towards idea stated are killing the innovations. We have to respect others idea, because the dangers of clash between the ideas on the teams are dangerous. Productivity and innovation quickly dies on those teams. Feel free to express and state your idea, because it may help to create a solution. Criticize the idea, not the people.

Sometimes, even the best plan in the world will go to waste, if there is not enough courage to execute the plan. There is certain situation that needed courage, rather than carefully crafted plan, it is important to state the right thing to do, rather than stand still and do the wrong things. Do what is right to do.

With chapter two wrapped up, now is the time to move to chapter three. Chapter three discusses about the importance of keep moving. Keep learning new things, and unlearning the things that is not needed anymore. It is up to ourselves to keep us informed of new technology and makes ourselves up to date, because the only one that cares about us is ourselves. There is nothing permanent except change. And in order to keep up with the change, we must continue to learn, a constant, small exposure is good, rather than a rare and long study session. The hardest part of learning a new thing is to let go all the habits we obtain in previous language or methods. We don’t have to be an expert in everything, but we should at least stay aware of the latest trend, and prepare for it.

There is another important thing about keeping yourself up to date, instead of making yourself the only member on the team which is smart, and updated enough, you should raise the bar for your team and for yourself. You will have a strong and capable team, which is able to overcome a difficult project much more easily. Don’t keep the knowledge to yourself!

Instead of keeping all the knowledge and habits from the past, we must know when the time to unlearn. It is dangerous to keep all the habits from the past into your relatively new software, because it will affect your design and coding techniques. Old habits are hard to break and even harder to notice, it is hard to let go, because the time and effort to refine the techniques are not small. It makes people thinks twice to let it go. When you learn a new technology, you must let go the old habit that hold you back!

We must realize that sometimes, we thought that asking a question would not solve the problem, wrong! In this book, we are encouraged to ask “Why??” Don’t just accept what you’re told. Keep questioning, until we finally understand the root of the problem.

Facing the uncertainty of the schedule and habit can affect our rhythm, mentioned in this part is how to keep our rhythm steady and ready for anything that comes next. It is always easier to act, when we already getting used to the rhythm. Always prepare for the things to come. Regular rhythms will make it harder to hide things, and gives you an excuse to have courage.