97 Things Every Software Architect Should Know
by Richard Monson-Haefel
Publisher: O'Reilly 2010
These articles are the original, unedited contributions for the book 97 Things Every Software Architect Should Know. Today's leading software architects present valuable principles on key development issues that go way beyond technology.
Home page url
Download or read it online for free here:
The problems to solve in software engineering are so complex or large, that a single developer cannot solve them anymore. This book is an introduction to the art of software engineering. It is intended as a textbook for an undergraduate level course.
by Jacob Burghardt - Flashbulb Interaction
A reference for product teams creating new applications for thinking work. Written for use during early, formative conversations, it provides teams with a broad range of considerations for setting the overall direction for their onscreen tools.
by Qi - thecodelesscode.com
An illustrated collection of (sometimes violent) fables concerning the Art and Philosophy of software development, written in the spirit of Zen koans. (For three days and nights the Java master did not emerge from his cubicle ...)
by Jasmin Blanchette - Trolltech
API is the set of symbols that are available to the users to write their applications. This manual presents the key insights into API design that were discovered through many years of software development on the Qt application development framework.