How Your Organization Is Killing Your Software - Improving Team and Product Architecture

How Your Organization Is Killing Your Software - Improving Team and Product Architecture

ChariotSolutions via YouTube Direct link

How to make sure things dont take longer than you think

5 of 26

5 of 26

How to make sure things dont take longer than you think

Class Central Classrooms beta

YouTube playlists curated by Class Central.

Classroom Contents

How Your Organization Is Killing Your Software - Improving Team and Product Architecture

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

  1. 1 Intro
  2. 2 Time dilation
  3. 3 Raffis background
  4. 4 How to make your team go faster
  5. 5 How to make sure things dont take longer than you think
  6. 6 The first thing that an org usually does
  7. 7 Technical debt
  8. 8 Rewriting
  9. 9 The 5 stages of rewrite
  10. 10 Do you have the right team
  11. 11 Compilers
  12. 12 Complexity vs Flexibility
  13. 13 Small Teams
  14. 14 Reaching Consensus
  15. 15 Making Product a dictatorship
  16. 16 Asynchronous Mode Transfer Networking
  17. 17 Product needs to be a dictatorship
  18. 18 Recap
  19. 19 Would Twitter be better if everything was still on Ruby
  20. 20 Teams and making smaller
  21. 21 Breaking into specialized teams
  22. 22 Avoiding code duplication
  23. 23 How big is a team
  24. 24 Single products
  25. 25 Architects
  26. 26 Open Source

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.