Summary

In this chapter, we looked at how to build for developers and the importance of cognitive load. Protecting users from undesired outcomes positively influences their cognitive load and gives them fewer concerns, and fewer things to debug if something goes wrong can help keep developers working efficiently. Additionally, the relationship between cognitive load and self-service was explored, and we took a look at some common tools and patterns to deliver a platform that meets the users where they are. If you were following along with a kind cluster, you may have even gained some hands-on experience with these recommendations. While we touched briefly on the security aspects of each of these topics, we’ll cover each of them and more topics in depth in the next chapter.