Greg Young - The Art of Destroying Software

Рет қаралды 8,472

9 ай бұрын

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 www.tretton37.com/

Пікірлер: 28

@duckydude20 2 күн бұрын

that's why goos, it takes this idea messages passing and showcases it. always thankful to these authors...

@vinceve43 7 ай бұрын

❤ Great legacy = transmitting micro debts ! The whole talk is great, pure wisdom. Thanks for sharing

@tretton37ab 5 ай бұрын

Thank you for taking the time to watch, like and comment. Means a lot!

@majormartintibor 5 ай бұрын

I'd make this talk mandatory to watch for every software developer.

@tretton37ab 5 ай бұрын

Putting this as a part of our onboarding "must watch" as we speak 🫡

@majormartintibor 4 ай бұрын

@@tretton37abwhen was this talk recorded btw?

@alexanderpodkopaev6691 2 ай бұрын

Won't help. They will listen to it on 2x speed, pretty much the same like they read only first page of Royce's at best. Most never bothered to find it.

@duckydude20 2 күн бұрын

it's like my ideas put forward in better way... same thing i realized, 12:37 thanks...

@ppercipio 5 ай бұрын

This is such a great talk. Thanks to Greg and the organizers of this talk.

@tretton37ab 4 ай бұрын

Glad you enjoyed it! Do you have any other topics on mind that you would like to hear more on?

@sysarcher 4 ай бұрын

Wow! This is the talk I need to give my team!!!

@tretton37ab 3 ай бұрын

This comment sparks so much joy

@ActualJosiahPreston 6 ай бұрын

Yay! Greg lives!

@tretton37ab 5 ай бұрын

Yeah boi!

@afailable 3 ай бұрын

In an event sourced system, does anyone know how to delete the code and still enable replayability of events? Keeping around old models for replayability doesn't seem like a great idea, but how do you do it otherwise?

@tretton37ab 3 ай бұрын

Great question! You've touched on a core challenge in event-sourced systems, tbh. The short answer for that would be "Event versioning" (meaning, we have to introduce new event versions for model changes, keeping old events compatible), "Upcasting" (transform old event versions to the current one on-the-fly, eliminating the need for old code) and "Archival" (archive obsolete models and events, using snapshots to capture system states). For the long one, we need to ping Greg 😅

@alexanderpodkopaev6691 2 ай бұрын

Geat talk!! Greg again confirmed that in IT there is too much teenager-like attitude 'won't learn from elders - my world is very different. Let's invent!'

@tretton37ab 3 күн бұрын

Great comment! 💚

@black-snow 16 күн бұрын

Much truth in there. However, not all debt is contained within one one-week bit. Then fixing that is not just a week. And when the behavior of the system emerges from the connection of small bits of behavior that's also nothing to rewire within one week.

@tretton37ab 3 күн бұрын

My reply here will be the number 1 words of choice for when we talk about the time frame or the outcome of a project - "It depends".

@mohammadrezataghipour2625 28 күн бұрын

Writing small programs inside a a big program is ok and not a new idea. But, overhead of managing and understanding too many small connected programs is still complex.

@mohammadrezataghipour2625 28 күн бұрын

As Greg suggests, small programs have more advantages than disadvantages, but things are not that much simple always and also things are not viewed technically always.. Programs size and in other words programs boundaries are political aspects in many companies… To be happy with it or not, it happens that around programs some form of ownership is created.. Finally, programs size are in most cases further than just a technical issue

@tretton37ab 3 күн бұрын

Facts!

@BillSeipel 4 ай бұрын

"Your tools affect your code". Exemplified by 'The medium is the message'. Mcluhan was right.

@tretton37ab 3 ай бұрын

true story

@elineporent7832 4 күн бұрын

Unix philosophy 30 years ago? More like 50 years ago

@tretton37ab 3 күн бұрын

How about we say 70 and shake on it? :D

@xbmcme9768 20 күн бұрын

I don't buy this. The idea that you write a ton of small programs such that they aren't interdependent upon each other is not practical for most applications. Any sufficiently complex program will have dependencies such that when X changes, you also have to change Y. In the worst case, this cascades and now you have to change A, B, and C.