101 Things Software Never Learnt in Architecture School

101 Things Software Never Learnt in Architecture School

Lightning Talk from #booster2015 conference

A6650bedde9088c804524bdd8e8a6b10?s=128

Marcin Floryan

March 11, 2015
Tweet

Transcript

  1. 101 Things Software Never Learnt in Architecture School 2015

  2. My wife is an Architect

  3. I am a Software Architect

  4. I am a Software Architect

  5. None
  6. Within 2 or 3 iterations you will have settled into

    the architecture you think is right and then be entering into a phase of tuning. -- Bob Martin
  7. None
  8. None
  9. What if… a consequence of applying architecture to software development

    are eventual, recurrent rewrites;
  10. None
  11. 001 Beauty is due more to harmonious relationships among the

    elements of a composition than to the elements themselves
  12. 010 Create architectural richness through informed simplicity or an interaction

    of simples rather than through unnecessarily busy agglomerations.
  13. 011 A proper building grows naturally, logically, and poetically out

    of all its conditions. software
  14. 100 Being process-oriented, not product- driven, is the most important

    and difficult skill for a designer to develop.
  15. 101 Properly gaining control of the design process tends to

    feel like one is losing control of the design process
  16. None
  17. Thank you! marcin.floryan.pl @mfloryan come and work with us