The Factory Pattern in Python // Separate Creation From Use

Comments · 265

• AR

  @ArjanCodes · 2 years ago · pinned

  💡 Here&apos;s my FREE 7-step guide to help you consistently design great software: <a href="https://arjancodes.com/designguide">https://arjancodes.com/designguide</a>.

  1

• JO

  @johnstanley1993 · 5 years ago

  For me as a data scientist your videos really stepped up my software development game. The Factor Pattern together with having abstract classes as interfaces is something I immediately applied in my current project. This is not something you typically learn in data science courses, even though I think this is crucial when willing to write code in a professional context. Thanks Arjan for sharing those valuable insights!

  103

• YA

  @yaczesuaff · 5 years ago

  I&apos;m binging your videos currently and (among other things) there&apos;s something I love: the examples are meaningful. They are practical, solve actual problems. Not your another off the mill tutorial with generic class C inheriting class B etc. Seeing that your example applications mimic actually doing something, makes it 100x easier to wrap the application logic and focus on the topic at hand. I&apos;m amazed.

  16

• VC

  @VCR47527 · 4 years ago

  Unsure if this is mentioned somewhere, but this is the GOF Abstract Factory pattern. Not to be confused with the GOF Factory Method pattern. The Abstract Factory pattern&apos;s goal is, as Arjan says, for grouping different class instantiations together. The Factory Method pattern is about extending the functionality of a class.

  57

• 00

  @002uzumaki · 5 years ago

  I just found out about you today while learning certain design patterns. Now, I started reading about factory patterns just a few hours ago and boom, you&apos;re here with the video. Thanks for the video. Maybe adapter pattern in the next video?

  45

• RI

  @richarddanipog4975 · 1 year ago

  Finally, a video that explains the factory pattern well and clearly. Thank you very much I so enjoy your presentation and delivery!

  1

• AS

  @AsenovMiroslav · 3 years ago

  I would like to propose the use of a factory dictionary approach, where the dictionary values store class names instead of actual instances. This can be more efficient, especially when creating instances is resource-intensive. The idea is to define a dictionary of factories like this:<br><br>factories = {<br> &nbsp;&apos;one&apos;: FactoryOne,<br> &nbsp;&apos;two&apos;: FactoryTwo<br>}<br><br><br>Later, when you need to create an instance based on a specific key, you can use the stored class names to instantiate the desired objects. This is done as follows:<br>return factories[key]()<br><br>With this approach, you optimize memory usage by storing class names, and actual instances are only created when needed.

  4

• YT

  @ytlagu2010 · 4 years ago

  I really like the idea where you first present the problem and show the solution. Most videos I watched rant about the theory but forgets to tell you the why part.

• CA

  @cabanford · 5 years ago

  I so enjoy your presentation and delivery. Great job in explaining &quot;why&quot; things are used and not just the typical &quot;how&quot; (which is what geeks who already grokk something tend to do). <br><br>I also like how you discuss what things a pattern doesn&apos;t do well and then you provide an alternative for such cases. ⭐⭐⭐

  9

• JO

  @JonMartins · 5 years ago

  I&apos;m addicted to your channel man!<br>Congrats. Cheers from Brazil.

• 9B

  @9boss6 · 5 years ago

  Thank you for what you are doing. It is really helpful. Keep going.

  4

• MD

  @mdunkman · 5 years ago

  I really enjoyed the video. Your pacing and amount of content is very good as a reference!<br><br>In a future video, could you clarify the differences between a Factory Pattern and a Builder Pattern? I feel like the builder is a way to collect factories, but I would enjoy seeing a worked example.

  8