Just a quick note to say that I've added some new essays to my Software Architecture for Developers book. They are:
- Software architects should be master builders: this talks about the importance of software architects needing deep technology skills and working as a part of the team.
- Technology is not an implementation detail: this is about why you shouldn't leave technology decisions as a after-thought.
- The need for sketches: this explains the importance of sketches in communicating the overall software architecture, both inside and outside of the immediate team.
- Would you code it that way?: this talks about the key question you need to ask yourself whenever you're designing software and visualising that design through sketches.
Leanpub does have the ability to e-mail readers whenever a new version of the book is published, but I try to only do this once or twice a month so as not to spam everybody. There is a version history at the back of the book though, which will tell you when new essays have been added plus it hyperlinks right to them. Hope you enjoy the new content.
About the author
Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.
You can find Simon on Twitter at @simonbrown ... see simonbrown.je for information about his speaking schedule, videos from past conferences and software architecture training.