Let’s say you’re getting froyo at your favorite local frozen yogurt shop. It starts simple: a dollop of vanilla, a dollop of chocolate. But wait—what if you want sprinkles? Or whipped cream? (Yes, you know it costs extra, and you don’t care.) Now maybe some cookie dough bites, a little caramel sauce, and why not— […]
Ever tried to plug an American hair dryer into a European socket? It doesn’t fit. That’s frustrating. But grab a travel adapter, and voila! Your hair dryer is back in action. This is a perfect analogy for the Adapter Pattern in software development. Read along to learn more about what the Adapter design pattern is,
Previously in this Design Patterns series, we examined the Observer pattern. This time around we’re diving into the Factory Design Pattern—a pattern that is great for cranking out objects when you need them, while keeping your code neat and tidy. Seriously, this is such a common pattern that you have to know it. What it is
In the last episode of this Design Patterns series we looked at the very simple Singleton. Now we’ll turn our attention to the frequently used and extremely useful Observer pattern. And of course you can instantly generate an Observer of your own by going to the PlantText Samples window and choosing “Design Patterns” and “Observer.”
In my last post on building Class Diagrams in PlantText, I mentioned I’d be kicking off a Design Patterns series. I figured we’d start simple and then build from there. You can’t get much simpler than the singleton pattern, right? So here we go. Just don’t ask ChatGPT to generate a singleton pattern for you
