• Let's talk about... State!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the State pattern. We'll review the pattern as a group and then open the discussion with the following question: If something has only two to three states, is it overkill to use the State pattern? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

    3
  • Let's talk about... Prototype!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Prototype pattern. We'll review the pattern as a group and then open the discussion with the following question: Part 1: When should this creational pattern be used over the other creational patterns? Part 2: Explain the difference between deep vs. shallow copy. After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

  • Let's talk about... Command!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Command pattern. We'll review the pattern as a group and then open the discussion with the following question: In the Motivation section of the Command pattern, an application's menu system is described. An application has a Menu, which in turn has MenuItems, which in turn execute commands when they are clicked. What happens if the command needs some information about the application in order to do its job? How would the command have access to such information such that new comamnds could easily be written that would also have access to the information they need? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

  • Let's talk about... Memento!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Memento pattern. We'll review the pattern as a group and then open the discussion with the following question: The authors write that the "Caretaker" participant never operates on or examines the contents of a memento. Can you consider a case where a Caretaker would infact need to know the identity of a memento and thus need the ability to examine or query the contents of that memento? Would this break something in the pattern? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

    7
  • Let's talk about... Chain of Responsibility!

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Chain of Responsibility pattern. We'll review the pattern as a group and then open the discussion with the following question: Part 1: How does the Chain of Responsibility pattern differ from the Decorator pattern or from a linked list?. Part 2: Is it helpful to look at patterns from a structural perspective? In other words, if you see how a set of patterns are the same in terms of how they are programmed, does that help you to understand when to apply them to a design? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

  • Let's talk about... Observer!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Observer pattern. We'll review the pattern as a group and then open the discussion with the following question: Part 1: The classic Model-View-Controller design is explained in Implementation note #8: Encapsulating complex update semantics. Would it ever make sense for an Observer (or View) to talk directly to the Subject (or Model)? Part 2: What are the properties of a system that uses the Observer pattern extensively? How would you approach the task of debugging code in such a system? Part 3: Is it clear to you how you would handle concurrency problems with is pattern? Consider an Unregister() message being sent to a subject, just before the subject sends a Notify() message to the ChangeManager (or Controller). After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

  • Let's talk about... Mediator!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Mediator pattern. We'll review the pattern as a group and then open the discussion with the following question: Since a Mediator becomes a repository for logic, can the code that implements this logic begin to get overly complex, possible resembling spaghetti code? How could this potential problem be solved? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

    3
  • Let's talk about... Bridge! πŸŒ‰

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the πŸŒ‰ Bridge pattern. We'll review the pattern as a group and then open the discussion with the following question: How does a Bridge differ from a Strategy and a Strategy's Context? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

  • Let's talk about... Adapter! πŸ”Œ

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Adapter pattern πŸ”Œ. We'll review the pattern as a group and then open the discussion with the following question: Would you ever create an Adapter that has the same interface as the object which it adapts? Would your Adapter then be a Proxy? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.

    4
  • Let's talk about... Proxy!

    Codurance

    The plan is to meet fortnightly to discuss and improve our understanding of design patterns. Initially we'll follow the 23 week guide covering the Gang of Four Design Patterns laid out by Joshua Kerievsky here - https://www.industriallogic.com/papers/learning.html The idea is that all attendees learn the pattern before the group meet, then during the meeting they consider various questions about the pattern. In doing so we'll benefit from the wisdom of the crowd and hopefully improve our understanding. We'll be following along to the Gang of Four patterns book so make sure to familiarise yourself with the section for pattern, you can grab a copy of it here -https://amzn.to/2HQaVM7 This session will be on the Proxy. We'll review the pattern as a group and then open the discussion with the following question: If a Proxy is used to instantiate an object only when it is absolutely needed, does the Proxy simplify code? After this we can take some time to break out into groups / pairs to explore the pattern further. Finally we'll wrap up with a retro to discuss any interesting points the group would like to explore further. Please note an in depth knowledge of patterns isn't required and all skill levels are welcome! A diverse range of perspectives is encouraged, however we'd recommend that attendees have studied the pattern that'll be discussed that week. Food and drink will be provided. πŸ™Œ Accessibility ------------------ The building we're in for this event unfortunately doesn't have disabled access. Please let us know if this will be an issue for you. We're working to find a more suitable venue for future events.