Book Image

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
Book Image

Agile Technical Practices Distilled

By: Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia

Overview of this book

The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You’ll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You’ll then learn to safely change the design of your code using refactoring. While learning these techniques, you’ll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.
Table of Contents (31 chapters)
Free Chapter
Section 1
Section 2
Section 3
Section 4
Chapter 21
License: CyberDojo

Bounded Rationality and Knowledge Sharing

Bounded rationality is the idea that, in decision making, the rationality of individuals is limited by the information they have, the cognitive limitations of their minds, and the finite amount of time they have to make a decision. The term was coined in the 1950s by Herbert A. Simon, and a lot has been written about its implications from an economic perspective. This simple concept plays a very important role in how we make decisions as a group.

Essentially, deductive rationality in a complex system tends to break down. The obvious reason is that beyond a certain level of complexity, the human mind reaches its natural limit to cope; hence, human rationality is bounded.

This is why it is easier to have an effective, small team rather than a large one. This is why we keep our classes small, we break user stories down into the smallest deliverable units, and we strive to reduce the responsibility of our bounded contexts. In turn, this limits...