Skip to content
0:00 / 0:00

#gregyoung#microservices#softwaredesign

Greg Young – The Art of Destroying Software

tretton37

827 subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 1 in engineering communities and 1 curated list.
  • Presented by Greg Young
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

18K views3 years ago2 recommendations

Software designSystems programmingSoftware architectureDesign patternsSimplicity and complexity

Greg Young argues that instead of building software to last forever, developers should design systems to be easily replaceable and disposable.

Greg Young delves into a counterintuitive approach with "The Art of Destroying Software." Challenging traditional beliefs, Young emphasizes the importance of dismantling and evolving software architectures to ensure adaptability, maintainability, and longevity. For deeper insights into this paradigm-shifting perspective on software development, navigate to tretton37.com/

Why it's here

2 people recommend this

What people say. Highly recommended as a classic talk on software design, microservices, and the benefits of build-to-replace architectures.

awesome-talkscurated list on GitHubRecommends

Under “Software Design”

The Art of Destroying Software by **Greg Young** (tretton37 2023) 42:30

u/MonochromeDinosaurin r/ExperiencedDevs • Recommends

On “Should we be trying to make microservices reusable?”

Never ever generalize before you need to. If you’re already doing microservices your goal should be to make them replaceable/easily rewritable and self contained, not generalizable. Essentially being able to throw them away after a quick rewrite is the ideal state. Now a template to scaffold services quickly might be useful to speed up development. link to this video