Knowledge should be viewed as an attribute of the system within which a software developer functions. For example, a non-Scrum team may include an architect and a QA who don't make any commits, but they still contribute their knowledge. Similarly, clients provide crucial information about the development needs and are part of the system the developer operates within. Therefore, we recommend measuring KEDE only at the system level, i.e., team, project, or company. However, factors such as happiness and cognitive load are assessed at the individual level. If a developer is working in an ensemble that fails to provide necessary knowledge, they may experience anxiety. Conversely, if the ensemble provides the required knowledge, the developer may experience a state of flow, or happiness. In these situations, the ensemble's collective work is reflected in the source code.