97 things every software architect should know
by Richard Monson-Haefel · first published 2009
5mentions
2recommended by
4HN commenters
2009–2024first – last mentioned
50% recommend50% neutral
In this unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de h ra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. You'll learn what top software architects think is important, and how they approach their projects.
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
97 Things Every Software Architect Should Know is a pretty good starting point. http://97things.oreilly.com/wiki/index.php/97_Things_Every_S...
on “Cause of today's Github outage” ↗97 Things Every Software Architect Should Know. Hands down. I just came across A Philosophy of Software Design and it looks good, but I haven't finished it yet. My experience has been that 'programming' is largely about learning best practices, single…
on “Ask HN: Books That Dramatically Transformed Your Programming Skills” ↗The printed book for the project 97 Things Every Software Architect Should Know has been released and is now available. This project was a community wide effort to articulate the keys points of software architecture.
on “Things Every Software Architect Should Know” ↗…finance, budgets, "business" language, operating models along with keeping my technical skills sharp In terms of resources: - Anything around learning to story tell and communicate effectively - The "97 Things Every Software Architect Should Know" essays - Your tech skills - write PoC apps, side-projects, try out new tech, learn to quickly grok strengths & weaknesses of tech
on “Ask HN: Software architects – what’s your typical day look like?” ↗…skills up to date, in lieu of more direct, cutting edge experience. To date I've studied the following, but don't have the free time to build anything of significance: - Web Application Security - 97 Things Every Software Architect Should Know (book) - Modularization / Single Responsibility / Programming Best Practices - A little bit of React - Test-Driven Development - Some administration related info in my bread-and-butter of choice (Java)…
on “Ask HN: Advanced topics of study for senior developers” ↗