Follow
George Fairbanks
George Fairbanks
Google
Verified email at georgefairbanks.com - Homepage
Title
Cited by
Cited by
Year
Just enough software architecture: a risk-driven approach
G Fairbanks
Marshall & Brainerd, 2010
1952010
Design fragments make using frameworks easier
G Fairbanks, D Garlan, W Scherlis
Proceedings of the 21st annual ACM SIGPLAN conference on Object-oriented …, 2006
722006
Ur-technical debt
G Fairbanks
IEEE Software 37 (4), 95-98, 2020
172020
The Risk-Driven Model
G Fairbanks
CrossTalk, 9, 2010
102010
Why can't they create architecture models like" Developer X"? An experience report
G Fairbanks
25th International Conference on Software Engineering, 2003. Proceedings …, 2003
92003
Ignore, refactor, or rewrite
G Fairbanks
IEEE Software 36 (2), 133-136, 2019
82019
Software architecture at a large financial firm
G Fairbanks, K Bierhoff, D D'Souza
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming …, 2006
82006
Architectural hoisting
G Fairbanks
IEEE Software 31 (4), 12-15, 2014
72014
The rituals of iterations and tests
G Fairbanks
IEEE Software 37 (06), 105-108, 2020
62020
Architecture Haiku
G Fairbanks
WICSA, 2011
62011
Design fragments
G Fairbanks
Carnegie Mellon University, 2007
62007
Software engineering environment support for frameworks A position paper
G Fairbanks
Workshop on Directions in Software Engineering Environments. Available …, 2004
62004
Better code reviews with design by contract
G Fairbanks
IEEE Software 36 (6), 53-56, 2019
52019
Designing the software systems of the future
L Northrop, I Ozkaya, G Fairbanks, M Keeling
ACM SIGSOFT Software Engineering Notes 43 (4), 28-30, 2019
52019
Code is your partner in thought
G Fairbanks
IEEE Software 37 (5), 109-112, 2020
42020
Intellectual control [Pragmatic Designer]
G Fairbanks
IEEE Software 36 (1), 91-94, 2019
42019
An architecturally-evident coding style: making your design visible in your code
GH Fairbanks
Proceedings of the ACM international conference companion on Object oriented …, 2010
42010
Garbage collect your technical debt
M Keeling, T Halloran, G Fairbanks
IEEE Software 38 (5), 113-116, 2021
32021
Why is it getting harder to apply software architecture?
G Fairbanks
IEEE Software 38 (4), 126-129, 2021
32021
Principle of Least Expressiveness
G Fairbanks
IEEE Software 36 (3), 116-119, 2019
32019
The system can't perform the operation now. Try again later.
Articles 1–20