Software Architecture vs. Code

Software Architecture vs. Code

GOTO Conferences via YouTube Direct link

Introduction

1 of 18

1 of 18

Introduction

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Software Architecture vs. Code

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Introduction
  2. 2 The intersection between software architecture and code
  3. 3 How do we communicate software architecture?
  4. 4 boundaries for TDD
  5. 5 Logical and development separated
  6. 6 BRAIN FREEZE!
  7. 7 The code is the embodiment of the architecture
  8. 8 Does your code reflect the abstractions that you think about?
  9. 9 Organisation of code
  10. 10 Diagramming tools See packages and classes rather than components
  11. 11 Abstractions on diagrams should reflect the code
  12. 12 Software developers are the most important stakeholders of software architecture
  13. 13 Did it start out that way?
  14. 14 Don't do unit testing!
  15. 15 A good architecture enables agility
  16. 16 The structure of your software and the decomposition strategy you use to get there are important
  17. 17 Think about how to align the software architecture and the code
  18. 18 If your software system is hard to work with, change it!

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.