Lodewijk Bergmans
@scalabledesign
useful/interesting/relevant content on software designs that can scale up with growing and changing systems.
You might like
interesting work simulating evolution shows: modularity results when trying to reduce the cost of connections technologyreview.com/view/428504/co…
why does it seem inevitable to get messy code, even necessary?--really nice talk by Brian Foote, feast of recognition: http://bit.ly/LpNOTH
composition is a basis for scalable development (and more important than abstraction) ow.ly/8YSbN
RT @polyomino: I hear all this talk about managing complexity. By then it's too late. You should have been cultivating simplicity.
How to manage software technical debt: (1) repackage it and sell it off as collateralized debt obligations, (2) await govt bailout.
my (september) HPL2011 presentation on a scalable design for a product line of embedded laser conversion systems slidesha.re/vEeADb
slideshare.net
Hpl2011.pptx
@wvanrheenen sheets keynote @janbosch are here: dl.dropbox.com/u/168578/LAC-2…
greefhorst #lac2011 discusses "architecture is about the essence & about restriction of design space": key ingredients of #scalabledesign !
#lac2011 keynote Jan Bosch: "we are moving from an integration-oriented to a composition-oriented world" #scalabledesign
#FREECO common agreement: criteria for determining best system decomposition strongly depend on context & stakeholders trese.ewi.utwente.nl/workshops/FREE…
"programs are not models of a part of reality, but when executed, they *are* a part of reality" Ostermann at #FREECO trese.ewi.utwente.nl/workshops/FREE…
so: a #scalabledesign yields 'code credit' (which is rather similar to Fowler's "design stamina" concept martinfowler.com/bliki/DesignSt…)
someone wondered about 'code credit'; that makes actual sense, as a metaphor for e.g. investing for future changes and extensions
Nice blogpost from Michael Stal about indicators for the quality (and scalability) of software architectures http://bit.ly/ii8lbJ
DesignStaminaHypothesis http://bit.ly/i23cal explains why #scalabledesign is not a (long term) investment for any real project, but survival
interesting post at http://bit.ly/fbMSEa: technical debt relates to accidental complexity, which is a cause for inaccurate effort estimates
implementing scalable designs requires more different & flexible compositions: check out the FREECO workshop at ECOOP: http://bit.ly/fYLmWX
who needs scalable design? SPLASH talk "The Case for Evolvable Software" provides a totally different perspective: http://bit.ly/hl4pjJ
United States Trends
- 1. #WWERaw 63.3K posts
- 2. Purdy 26.1K posts
- 3. Panthers 35.7K posts
- 4. Bryce 19.6K posts
- 5. 49ers 37.9K posts
- 6. Canales 13.1K posts
- 7. #FTTB 5,345 posts
- 8. Mac Jones 4,746 posts
- 9. Penta 9,638 posts
- 10. #KeepPounding 5,238 posts
- 11. Niners 5,409 posts
- 12. Gonzaga 2,941 posts
- 13. Gunther 14K posts
- 14. Jaycee Horn 2,643 posts
- 15. Jauan Jennings 1,932 posts
- 16. Amen Thompson N/A
- 17. #RawOnNetflix 2,095 posts
- 18. Moehrig N/A
- 19. Logan Cooley N/A
- 20. Ji'Ayir Brown 1,284 posts
You might like
Something went wrong.
Something went wrong.