Yet Another Programming Blog

These are my highlights while reading Robert C. Martin's book Clean Agile: Back to Basics. Preface Uncle Bob starts with a disclaimer. This book is not a work of research. Think of it as a memoir. I knew this upfront and I was looking forward to see him grumbling about what the world has done to his Agile. Big things don't get done by big teams. Big things get done by many small teams collaborating while doing many small things. This is what programmers in 1950s and 1960s new instinctively and this is what got lost in 1970s. Couple of folks reinvented this idea and called it 'Agile'. It has been nearly 20 years from the start of this movement and Martin thinks it is already time for yet another reboot. Acknowledgments I usually don't read Acknowledgments, but these ones have exceptional list of names. It is basically a to-do list for following and reading the mentioned people. Ward Cunningham, Kent Beck, Martin Fowler, Ken Schwaber, Mary Poppendick, Ron Jeffries and...

These are my notes to the Robert Martin's book Agile Software Development: Principles, Patterns and Practices. Chapter 1 - Agile Practices Don't immediately buy the priciest database there is, but try the flat files first. The same goes for VCSs. Look at the tools with the jaded eye. The first Law of Documentation: Produce no document unless the need is immediate and significant. Fixed-time fixed-price projects don't work. The best contracts are those which specify how customers and developers should work together. We should plan only weeks ahead. We should have rough plans for the months ahead and almost no plans for years ahead. The less functionality the initial release has, the more quality the final product will have. Progress is measured in software done: 30% done means 30% of functionalities are working. Chapter 2 - Overview of Extreme Programming Pair programming does not decrease the efficiency of the team, but it dramatically improves the defect r...