• Solutions
    • I Can Help
      • Define
      • Educate
      • Integrate
      • Advise
    • Consultation
      • Assessments
      • Design Reviews
      • Code Inspections
      • Ongoing Support
    • Training Classes
      • Training Schedule
      • On-Site Classes
      • Online Training
      • Customized Coaching and Mob Facilitation
    • Learning Roadmap
      • Developer Essentials Training
        • Agile Analysis and Design Patterns
        • Hands-On: Extreme Programming Practices
      • Scrum Framework Developer Essentials
      • Design Pattern Developer Essentials
      • Object-Oriented Analysis and Design Patterns
      • Scrum Software Developer Essentials
      • Agile Software Developer Essentials
      • Agile Software Developer Intensives
    • Speaking
      • Beyond the Legacy Code Crisis
      • Five Developer Practices for Agile Software
      • Writing High Quality, CLEAN Code
      • Essential Scrum Developer Practices
      • Improving Your Scrum Process
      • The Agile Development Advantage
    • Testimonials
    • Clients
  • Resources
    • Blog
    • My Book: Beyond Legacy Code
    • Bibliography
    • Referral Program
    • Associates
  • Contact
    • Contact Me
    • Schedule A Call
    • About
  • Schedule A Call

Polymorphism

  1. Home
  2. Blog
  3. Polymorphism

2025 Public Training Schedule

June 23 26, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions Online

July 22 – 25, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions Online

Register Now
Or schedule a private class
Course Descriptions
  • Developer Essentials Training
    • Agile Analysis and Design Patterns
    • Hands-On: Extreme Programming Practices
  • Object-Oriented Analysis and Design Patterns
  • Scrum Software Developer Essentials
  • Agile Software Developer Essentials
  • Agile Software Developer Intensives
Follow me on Twitter:

Follow @ToBeAgile

Blog Post Categories
  • Announcements {19}
  • Articles {2}
  • Bits and Pieces {74}
  • Blogosphere {1}
  • Bonuses {2}
  • Build in Small Batches {27}
  • Collaborate {38}
  • Create CLEAN Code {34}
  • Implement the Design Last {11}
  • Integrate Continuously {30}
  • Off-Topic but Interesting {3}
  • Rants {82}
  • Refactor Legacy Code {24}
  • Say What, Why, and for Whom Before How {22}
  • Seven Strategies {38}
  • Specify Behaviors with Tests {17}
  • Write the Test First {27}
Archives
  • 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • 2022
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • 2021
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • 2020
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • 2019
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • 2018
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • 2017
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • 2016
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • 2015
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • 2014
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • 2013
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • 2012
  • December 2012
  • Privacy Policy

    (c) 2025 To Be Agile

    • October 21, 2020 ( 2 comments )
    • Articles

    Polymorphism is a big word for an important technique in object-oriented programming to help make code extendable. Rather than expressing business rules as conditional statements in code, we move them into factories and use them to instantiate objects that do the actions we want to take.

    We need to know different things when we create an object versus when we use an object so separating these two activities can improve encapsulation and code cohesion. To create an object, you must know the object’s type. To use it you must know the signature of the methods you want to call, but you don’t have to know the object’s type, you could know the type of its parent or an interface that it implements. Polymorphism can give you the freedom to extend a type without breaking existing code.

    This is also one of the key techniques in doing emergent design because it’s natural for a lot of good design to come out of refactoring when we build software in this way. We can come up with a better implementation for code that we already have under test so it’s far easier and more reliable to refactor than to write new code that’s not under test.

    This is very much in line with my views on how to do test-first development where we write a test that fails and then try to make it succeed as quickly as possible, using the simplest implementation necessary, then work on refactoring it to make it more robust and maintainable. This is definitely a far easier and less error prone approach to writing code but few developers make use of it.

    Of course, there’s a lot more to emergent design than just putting business rules in factories, although that is an important and not well understood aspect of good object-oriented programming, if not Agile development, in general. The reason for this is that the more differences we can handle as an issue of instantiation, the less we have to do with it in our production code, and that greatly simplifies the production code.

    For example, a circle, a square, and a triangle are very different shapes and the way they’re drawn is completely different, but if I can handle those differences and draw them up on the screen as an issue of instantiation then I can treat them all the same way in my production code and move them or erase them or fill them with the same calls.

    We refer to this as type encapsulation because we’re hiding the specific type that we’re working with from the one who’s using it. For example, the drawing program is unaware if it’s working with a circle or rectangle, all it needs to know is that it’s dealing with a shape and that a shape can be moved or resized. This not only simplifies the drawing code tremendously but it also makes the code far more general purpose because we can add new shapes and as long as they’re able to be moved and resized, they can interact with and be manipulated by the drawing program without having to change the drawing program at all. This type of extensibility is essential for emerging software.

    The way object-oriented systems achieve this level of extensibility is through polymorphism. A polymorphic method is simply a method that shares its name with methods in other objects, which are typically sibling objects.

    For example, a rectangle and a circle may have a polymorphic method called resize. The way we resize a rectangle versus a circle are different so each of the shapes will be responsible for resizing themselves in a different way that’s appropriate for them. But because each of them has a resize method, the drawing program can simply tell the shape to resize and not be involved in the specific implementation details of resizing because all shapes have the ability to resize.

    A triangle is a shape, as is a circle and a rectangle. They are kinds of shapes because they share a common interface to polymorphic behavior. Circles and triangles and rectangles are represented in software as classes. There’s also the notion of an abstract class that represents a group of concrete classes. For example, a shape can be an abstract class. Abstract classes typically have some abstract methods that represent the method signature, or the way it’s called, but not what it does. The body of an abstract method is defined in the subclasses of the abstract class, for example a rectangle or a circle or a triangle.

    Callers, like the drawing program, can only use concrete classes such as rectangles or circles or triangles, but they can hold those concrete classes in an abstract upcast type like shape and not have to know what specific derivation they’re using. This gives us a way of decoupling callers from the specific implementations they use. It’s one of the main ways that we “design to interfaces” in software development.

    It helps to know the principles of good object-oriented programming. And it helps to know about design patterns and refactoring. All of these things together help us do emergent design efficiently. The most valuable part of doing emergent design is employing good techniques around breaking dependencies and encapsulating details. By mastering these techniques, we can be armed with tools that will help us in many situations, especially when we don’t know some of the requirements, or they’re likely to change in the future.

    {2 Comments }

    • Kang says:
      November 2, 2020 at 8:04 pm

      Thank you David for this great post. Big help for clarifying the concepts. It brought me back to review the part of Factory in the Design Pattern section from the class.

      Reply
      • David Bernstein says:
        November 8, 2020 at 8:49 pm

        You are welcome. I’m glad to know that you found value in my post! Best, David.

        Reply

    Previous Post: « Pair Programing Paradoxes

    Next Post: How Small should a Story Be? »

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Solutions

    I Can Help
    • Define
    • Educate
    • Integrate
    • Advise

    Consultation
    • Assessments
    • Design Reviews
    • Code Inspections
    • Ongoing Support

    Testimonials Clients

    Resources

    • Blog
    • My Book: Beyond Legacy Code
    • Referral Program
    • Associates


    Read my book!
    Schedule a Call

    Training

    • Training Schedule
    • Learning Roadmap
    • On-Site Classes
    • Online Training
    • Customized Coaching and Mob Facilitation

    Course Descriptions
    • Developer Essentials Training
      • Agile Analysis and Design Patterns
      • Hands-On: Extreme Programming Practices
    • Object-Oriented Analysis and Design Patterns
    • Scrum Software Developer Essentials
    • Agile Software Developer Essentials
    • Agile Software Developer Intensives

    Copyright 2025 © To Be Agile. All rights reserved. Privacy Policy.

    This website uses cookies to improve your experience. I'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    SAVE & ACCEPT