The essays are about programming, but focused more on personal process and professional development. My intent was never to just teach coding as there are tons of resources for any given programming language. I haven’t heard as much discussion about the non-coding activities that I think are still very much a part of producing excellent software. Most books on the topic of process focus much more on the organization. While I try to relate my essays to that scale, I also really try to give much more personal guidance. After all, from project to project, organizations and their processes may change, but all throughout your career, what you bring to the table is constant.

Your confusion does suggest I need to describe the forthcoming volumes more clearly and adjust the marketing to make the focus of the content clear. In retrospect, I can definitely see why someone listing to the promo or reading the podiobook description would think they are subscribing to a work on how to write source code as opposed to what the book actually contains.

Thanks for the feedback!