#url 地址：http://97-things.near-time.net/wiki/other-things-software-architects-should-know
1. Architects should be Pragmatic by John Davies
2. Applications are for making users as effective as possible by Ben Geyer
3. Community by Evan Cofsky
4. Know all the rules -- so you know which ones you're breaking by Kevin Bedell
5. Not all problems are solved with a layer of abstraction by Apu Shah
6. Learn to be humble by Apu Shah
7. Architecture is more than just the pieces byPaul W. Homer
8. Responsible explorer by George Malamidis
9. Design for limited resources by Mncedisi Kasper
10. The fastest system components are the one's that aren't there by John Tullis
11. The closer the better by John Tullis
12. It's not an architecture if it can't be managed by Dan Pritchett
13. Your project does not exist in a vacuum by Charles Martin
14. Design for needs, not wants by Claudio Perrone
15. Consider application failures, and design for ease of recovery by Stephen Jones
16. Risk priority by George Malamidis
17. Test the Architecture by Matt McKnight
18. An architect's responsibility never finishes after the architecture is created by Kamal Wickramanayake
19. Change is a constant; architecture needs to be adaptable and the architect needs to be a change driver by Daniel Noguerol
20. One alternative is a trap, two are a dilemma, three are freedom by Lior Bar-On
21. Work on thy soft skills just as much as on your hard skills by Arnon Rotem-Gal-Oz
22. Examine the sourcing of calculated fields by Stephen Jones
23. Feel it by Mahomedalid Pacheco
24. No, the goal is not the code nor the design by William Martinez
25. Quality is a feature by Sam Gardiner
26. Good Requirements Are Boring by Eben Hewitt
27. Don’t Make Worlds, Make Containers for Worlds by Eben Hewitt
28. Architecture = SPICE RTM by António Melo
29. Know your limitations by Peter Gillard-Moss
30. Tarchitects vs. Marketects vs. Carhitects by Yi Zhou
31. Read Philoophy (and related Arts) by Keith Braithwaite
32. Prioritize Challenges to Drive Architecture Decisions by Charlie Alfred
33. Reduce Conceptual Distance by Charlie Alfred
34. The User Interface drives the User Experience by Burk Hufnagel
35. If you're unwilling to be hands-on, maybe you should keep your hands off by Barry Hawkins
36. Lead by Influence by Travis Illig
37. Software Should Be Invisible by Eben Hewitt
38. Requirements are not the measure of success but the beginnings of a conversation by Christopher Dempsey
1. Architects should be Pragmatic by John Davies
2. Applications are for making users as effective as possible by Ben Geyer
3. Community by Evan Cofsky
4. Know all the rules -- so you know which ones you're breaking by Kevin Bedell
5. Not all problems are solved with a layer of abstraction by Apu Shah
6. Learn to be humble by Apu Shah
7. Architecture is more than just the pieces byPaul W. Homer
8. Responsible explorer by George Malamidis
9. Design for limited resources by Mncedisi Kasper
10. The fastest system components are the one's that aren't there by John Tullis
11. The closer the better by John Tullis
12. It's not an architecture if it can't be managed by Dan Pritchett
13. Your project does not exist in a vacuum by Charles Martin
14. Design for needs, not wants by Claudio Perrone
15. Consider application failures, and design for ease of recovery by Stephen Jones
16. Risk priority by George Malamidis
17. Test the Architecture by Matt McKnight
18. An architect's responsibility never finishes after the architecture is created by Kamal Wickramanayake
19. Change is a constant; architecture needs to be adaptable and the architect needs to be a change driver by Daniel Noguerol
20. One alternative is a trap, two are a dilemma, three are freedom by Lior Bar-On
21. Work on thy soft skills just as much as on your hard skills by Arnon Rotem-Gal-Oz
22. Examine the sourcing of calculated fields by Stephen Jones
23. Feel it by Mahomedalid Pacheco
24. No, the goal is not the code nor the design by William Martinez
25. Quality is a feature by Sam Gardiner
26. Good Requirements Are Boring by Eben Hewitt
27. Don’t Make Worlds, Make Containers for Worlds by Eben Hewitt
28. Architecture = SPICE RTM by António Melo
29. Know your limitations by Peter Gillard-Moss
30. Tarchitects vs. Marketects vs. Carhitects by Yi Zhou
31. Read Philoophy (and related Arts) by Keith Braithwaite
32. Prioritize Challenges to Drive Architecture Decisions by Charlie Alfred
33. Reduce Conceptual Distance by Charlie Alfred
34. The User Interface drives the User Experience by Burk Hufnagel
35. If you're unwilling to be hands-on, maybe you should keep your hands off by Barry Hawkins
36. Lead by Influence by Travis Illig
37. Software Should Be Invisible by Eben Hewitt
38. Requirements are not the measure of success but the beginnings of a conversation by Christopher Dempsey
扫一扫
2033
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
