Great blog post by Agile Journeyman about Martin Fowler's Design Stamina Hypothesis & the Technical Debt Quadrant.
Constantin Kostenko
Firebrand Architect®
Wednesday, December 28, 2011
Subscribe to:
Post Comments (Atom)
Subscribe To
About Me
- Firebrand Architect®
- “The firebrand is the person who recognizes what is natural, what is organic, what is alive and vital in life... Being a firebrand is a way of raising temperatures and creating conflict, and turbulence ... The motive of the firebrand is not to attack or destroy others but to bring to light a basic truth, to take a stand … the firebrand chooses to be different when being different represents a truth, when being different guides the fulfillment of basic human values and actualization of one’s potentials” - Moustakas, Clark. This blog is an application of this philosophy to the software architecture discipline. View complete profile for additional details.
Blog Archive
-
►
2009
(45)
-
►
October
(13)
- adding complexity to reduce complexity
- See the ecosystem, not the forrest
- Architecting Windows 7
- What kind of leader are you?
- PDC 2009
- You, as an architect, must take the initiative
- Interviewing future leaders at Carnegie Mellon - H...
- You can't rely on your knowledge of patterns alone...
- Example of a solution not fit for purpose
- What exactly is "fit for purpose"
- Software Engineering education for your clients an...
- Writing down solution concept - a practical quick ...
- Using consultants for big picture insight
-
►
October
(13)
Links
Labels
- human aspects of software architecture (39)
- software architecture (36)
- software architect (23)
- Responsible Software Architecture (22)
- thinking (21)
- lessons learned (19)
- software architecture discipline (17)
- team work (17)
- Solution architect (14)
- management (13)
- stakeholders (13)
- Constantin Kostenko (12)
- communication (12)
- software architecture paradigm (11)
- politics (10)
- quality attributes (10)
- software architecture documentation (10)
- Business architecture (8)
- events (8)
- behavior (7)
- Enterprise Architecture (6)
- patterns (6)
- software architecture definition (6)
- COTS (5)
- information sharing (5)
- meetings (5)
- ATAM (4)
- leadership (4)
- Cloud Computing (3)
- SOA (3)
- Security (1)
- globalization (1)
- software (1)
- software engineering (1)
0 comments:
Post a Comment