The Business Versus the Angry Architect, 74. /H [ 1650 230 ] 0000008384 00000 n /Type /Font /ImageB << 222 222 222 222 222 0 0 222 0 0 There Is No One-Size-Fits-All Solution, 13. 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts. 3 35 Chances Are, Your Biggest Problem Isn’t Technical, 4. stream >> /LastChar 211 /ExtGState << Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. 0 0 0 0 0 556 611 500 611 556 This book tells you what top software architects think is important and how they approach a project. /quoteright/U/nine/seven/six/plus/I/J/X/eight/numbersign/parenleft/parenright/K/slash/percent/semicol\ endobj 4 0 obj >> 0 0 0 0 0 0 500 0 0 0 /CapHeight 722 /ABCpdf 7010 /OP false 0 584 278 333 278 444 556 556 556 556 /O 6 0 0 0 278 0 278 278 0 0 0 /CapHeight 722 500 0 0 0 0 278 0 0 0 0 /XObject << Stable Problems Get High-Quality Solutions, 79. As could be expected, the Every [...] Should Know part of the title is quite a stretch, but there's some good advice here and there. Servants, 5. /OPM 1 278 500 500 222 222 444 222 722 500 500 startxref /MediaBox [ 0 0 612 792 ] 0000007558 00000 n 97 Things has 4 repositories available. >> The essay “97 things every software architect should know” discuss what it means to be a software architecture. << 5 0 obj /FirstChar 32 10 0 obj 0 0 0 222 0 222 222 0 0 1000 /Text W n xref 21 0 obj Robert C. Martin, Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”) By applying universal rules …. Find and Retain Passionate Problem Solvers, 96. x�c``P```+���� 6(@a %%EOF endobj Choose Your Weapons Carefully, Relinquish Them Reluctantly, 84. 13 0 obj endobj /Widths [ 222 333 0 444 444 778 667 250 278 278 0000006256 00000 n /FirstChar 48 /FontName /ICAFIF+Univers-Bold 0000008649 00000 n 24 0 obj /Widths [ 500 500 500 500 500 500 500 500 500 500 ] >> 333 333 333 333 333 0 0 333 0 0 Reuse Is About People and Education, Not Just Architecture, Are Convinced That It’s Better Than Doing It Themselves, 34. /LastChar 213 << /op false >> >> /ItalicAngle 0 /F1 16 0 R Don't put your resume ahead of your requirements - 97 Things Every Software Architect should know. /BaseFont /ICAFGC+Goudy /OpenAction [ 6 0 R 556 556 556 556 556 556 278 0 0 0 /XHeight 505 /Ascent 745 /T 68950 /Im9 28 0 R /Encoding /MacRomanEncoding /BitsPerSample 8 0 444 788 611 611 556 611 500 444 611 0000000012 00000 n << If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading. /ItalicAngle 0 Focus on Application Support and Maintenance, 59. /XHeight 505 0 0 0 0 0 0 0 0 0 0 166 Write Code As If You Had to Support It 0000010924 00000 n Choose Frameworks That Play Well with Others, 90. Simplify Essential Complexity; Diminish Accidental 722 278 556 667 556 944 778 778 611 778 0 0 0 333 0 333 333 0 0 0 Kevlin Henney has created a nice book "97 Things Every Programmer Should Know" of the selected 97 essays. /Ascent 722 0 0 0 0 0 0 222 0 0 0 Pearls of wisdom for programmers collected from leading practitioners. 611 611 389 500 333 611 556 833 556 556 . Aditya Y. Bhargava, Grokking Algorithms is a friendly take on this core computer science topic. In this post I summarize the chapters I found interesting. endobj /Encoding /MacRomanEncoding 3 0 obj /FontFile3 33 0 R If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading. /Type /FontDescriptor /CharSet (/space/I/n/g/r/a/m/P/u/b/l/i/s/h/e/S/v/c/parenleft/eight/six/parenright/four/zero/hyphen/five/three/\ /Ascent 722 /CharSet (/space/three/four/five/six/seven/nine/one/zero/two/eight) /StemH 120 /StemH 73 Before Anything, an Architect Is a Developer, 66. The book is the collective contribution of technical architects from all over the world working across the full range of domains. /Widths [ 222 0 0 0 0 0 0 250 0 0 /Type /Font 0000002311 00000 n /Prev 68940 >> 0 0 0 0 0 0 0 0 0 0 /FirstChar 32 0000002429 00000 n /Type /FontDescriptor 97 Things Every Software Architect Should Know Collective Wisdom from the Experts edited by Richard Monson-Haefel • Concise and to the point—each principle is followed by a brief explanation • Allows readers to learn what top software architects think is important and provides insights into the way they approach problems /Subtype /Type1 /Subtype /Type1