2024-04-19 - Design Patterns - Chewing the Fat 📈

[sethdaily]

Hey SSWers,

1. What's your favorite design pattern?
2. Which one are you most keen to try?

Discuss below ⬇️

https://www.ssw.com.au/rules/common-design-patterns

[Freego1783]

Design Patterns did not really interest me in school but then I realized I was following them without really knowing it 😁

[ricksu978]

1. Observer Pattern, I love to see interactions between subscribers and publisher.
2. State Pattern.
   In my past experience, the State Pattern is the least pattern I have implemented. I would love to try this pattern and apply it to a real system.

[brydeno]

1. Unit of Work because it forces you to think about what "needs" to be done for a given interaction
2. Building Repositories cleverly is typically the most interesting and challenging.

[matt-goldman]

1. Singleton 🤖 (https://chat.openai.com/share/e90433fe-8005-4ff7-b317-64034803d6c6)
2. Specification pattern - I like the concept but have not used it yet. I want to understand the practical applications better.

[AntPolkanov]

Q: Why did the singleton feel lonely in a multi-threaded environment?

A: Because it couldn't handle being shared! 😜

[tkapa]

DI is cool but I don't necessary think that it's the most important.
I think that Specification sounds kind of cool.

[AlexRothwell]

1. What's your favorite design pattern?

Dependency injection - it usually greatly improves the testability of a class and allows me to be more confident in its correctness

2. Which one are you most keen to try?

I've not really touched the specification pattern so I'd be interested to see how that fits in

[jakebayliss]

1. Dependency Injection
2. State Pattern - Sounds like it would be fun to build

[jaydenalchin]

[ncn-ssw]

1. What's your favorite design pattern?

Spaghetti - easiest to improve on.

Actual answer is I don't have 1 - the patterns are conceptual tools, many of them attending to different problems. I try to use the pattern most applicable to the problem, with a bias towards patterns already in that code base when 2 patterns will provide similar benefits.

2. Which one are you most keen to try?

I find this a strange question. I've used nearly all of the patterns listed and the choice of pattern would be dependent on the problem rather than the pattern I wanted to implement.

[ozdemir-mehmet-cer]

Would be good to devote an SSW training course to patterns and how they're applied to our reference solutions

[leahy268]

Almost fell asleep watching the video. Maybe it all made sense if you knew all those design patterns already but if you didn't then either the rule or the video - otherwise I found it a pretty boring one.

[stephanfakossw]

Does not make much sense to, but I'm not a dev :-)

[alexleessw]

NA - I'm not a developer
Have an awesome day everyone 😊

[Calinator444]

1. Depencency Injection - It improves code maintainability to abstract away the implementation details of a function. For instance if I have checkout class with a payment_handler class injected I no longer need to be concerned with how the payment_handler makes a payment, I only need to be concerned with it's output. This also makes it easier to unit test checkout because I've already seperated out all of the payment logic.

2. Mediator patten - I haven't really been on a project up until now that was large enough to dictate how classes communicate with one another.

[cvionnet]

1. Dependency Injection
2. Specification Pattern - I just heard about it a few weeks ago, thanks to @william-liebenberg

[christoment]

My favourite one is DI - Keen to see more State Pattern, and how to compromise it with the performance impact on a large scale :)

[arig2024]

Not a dev sounds interesting... until the monotone puts me to sleep. Im sure someone can fix that.

[jernejk]

1. What's your favorite design pattern?
   Fluent API where you allow developers to create a chain of actions. LINQ, the way we configure .NET applications, EF Core, etc.

A well-designed, fluent API can make builder patterns, factories, queries, DIs, etc., look much more readable and maintainable.

var obj = new BuilderThing()
    .AddConfig(...)
    .RegisterXY(...)
    .Create()
    .Run();

This pattern can make complex code look easy to use.

2. Which one are you most keen to try?
   The query specification pattern to abstract LINQ queries as request objects.

Although, @wicksipedia mention of Flyweight does make me curious.

[jerryluossw]

Favorite design pattern - Factory pattern, this is the first pattern I know of
Most keen to try - Observer Pattern

[Marxoz]

1. Factory Pattern. I like to hide the chaos behind the scenes.
2. Specification. Have not used it before.

[jimmidier]

1. Inversion of Control - The cornerstone of modular and multi-layered projects
2. Facade - Haven't tried before

[SofieHong]

N/A - I'm not a developer 🤣

[Aibono1225]

What's your favorite design pattern?

DI

Which one are you most keen to try?

Mediator

[tino-liu]

What's your favorite design pattern?

Dependency Injection

Which one are you most keen to try?

Facade

[babakamyljanovssw]

1. Dependency Injection and Observer
2. Specification - havent't heard or used this pattern before, sounds interesting

[bradystroud]

1. What's your favorite design pattern?

No favorite - I use them case by case

2. Which one are you most keen to try?

None in particular. The next one I use will be the next one I think I need

[danielmackay]

1. What's your favorite design pattern?

Inversion of Control is simple, yet incredibly powerful. Also really like the MediatR pattern.

2. Which one are you most keen to try?

I've used many of these patterns, but the State pattern seems like the most interesting one that I haven't tried yet.

[MarcusIrmscherSSW]

This is way over my head, but do see how important using a Design Pattern can be.

[ozairashfaqueSSW]

1. What's your favorite design pattern?

Dependency Injection

2. Which one are you most keen to try?

State Pattern

[PothieuG]

What's your favorite design pattern?
-> Dependency Injection