Read John Ousterhout's "A Philosophy of Software Design" yesterday; highly recommended. Pull of pragmatic advice for identifying and managing complexity in software systems _and_ avoids dogma. My kind of principles-based design!

Sign in to participate in the conversation
Ann Arbor/Ypsilanti & Friends Community

Hi there! is a Mastodon community intended for people living/working/studying in and around Ann Arbor (including Ypsi and elsewhere!) and their friends. Please read more about this community here, including this site's rules and other important information.