genehughson

16 ms·

91.
Negotiating Estimates(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
92.
‘Customer collaboration over contract negotiation’ and #NoEstimates(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
93.
Cause and Effect – Cargo Cults and Carts Before Horses(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
94.
Microservices, Monoliths, and Conflicts to Resolve(genehughson.wordpress.com)
2 points by genehughson 11y ago|0 comments
95.
Who Needs Architects? Because Complexity Emerges(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
96.
Who Needs Architects? Because YAGNI Doesn’t Scale(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
97.
Microservices, SOA, and EITA: Where to Draw the Line? Why to Draw the Line?(iasaglobal.org)
2 points by genehughson 11y ago|0 comments
98.
Maybe It's Time for Customer Driven Development(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
99.
Estimates – Uses, Abuses, and That Credibility Thing Again(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
100.
#NoEstimates – Questions, Answers, and Credibility(genehughson.wordpress.com)
2 points by genehughson 11y ago|0 comments
101.
Modeling the Evolution of Software Architecture(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
102.
Microservices, Monoliths, Modularity – Shearing Layers for Flexibility(iasaglobal.org)
1 points by genehughson 11y ago|0 comments
103.
When Reality Gets in the Way – Applying Systems Thinking to Design(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
104.
Cargo Cult Architecture(genehughson.wordpress.com)
5 points by genehughson 11y ago|0 comments
105.
Planning and Designing – Intentional, Accidental, Emergent(genehughson.wordpress.com)
2 points by genehughson 11y ago|0 comments
106.
Microservice Mistakes – Complexity as a Service(iasaglobal.org)
1 points by genehughson 11y ago|0 comments
107.
Who Needs Architects? – Are You Committed to Reaching Your Goals?(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
108.
Who Needs Architects? – Monoliths as Systems of Stuff(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
109.
Microservices – Sharpening the Focus(genehughson.wordpress.com)
3 points by genehughson 11y ago|0 comments
110.
Fixing IT – Remembering What They’re Paying For(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
111.
Law of Unintended Consequences – Security Edition(genehughson.wordpress.com)
1 points by genehughson 11y ago|0 comments
112.
Who Needs Architects? Who’s Minding the Architecture?(genehughson.wordpress.com)
1 points by genehughson 12y ago|0 comments
113.
Laziness as a Virtue in Software Architecture(genehughson.wordpress.com)
1 points by genehughson 12y ago|0 comments
114.
Institutional Amnesia, Cargo Cults and Software Development(genehughson.wordpress.com)
1 points by genehughson 12y ago|0 comments
115.
Are Microservices the Next Big Thing?(genehughson.wordpress.com)
2 points by genehughson 12y ago|0 comments
116.
What Makes a Microservice “Micro”?(genehughson.wordpress.com)
3 points by genehughson 12y ago|0 comments
117.
Microservice Principles, Technical Debt, and Legacy Systems(genehughson.wordpress.com)
3 points by genehughson 12y ago|0 comments
118.
Of Blind Men and Elephants and Excessive Certainty(genehughson.wordpress.com)
1 points by genehughson 12y ago|0 comments
119.
Microservice Architectures aren’t for Everyone(genehughson.wordpress.com)
2 points by genehughson 12y ago|0 comments
120.
Fixing IT – Microservices and DevOps to the Rescue?(genehughson.wordpress.com)
1 points by genehughson 12y ago|0 comments

More ›