Am I right in thinking that one would only use the Builder pattern if it's very unlikely that they would need to add to the steps defined in the interface? I also think the example I've given means we are in danger of creating a 'fat' interface. I'm just learning about object oriented programming, so please correct me if I'm wrong, but I think the Director doesn't follow the Open/Closed principle. This means that every single one of the concrete builder classes would have to be amended to implement the new method, even though most of them won't need it. Using the example you provided, for each new feature we would need to add a new method to the interface IBicycleBuilder, e.g. In other words, we think that the Director needs to be open for extension. We also think they might add more new features in the future. For example, suppose we know that manufacturers are planning to include a new feature, e.g. My question is about how we should proceed if we know that the Director is likely to need new steps in the future. Member 14118759 15-Jan-19 5:11 15-Jan-19 5:11 Hi Snesh, Thanks for your article, it really helped me. It actually needs loads of patience and practice. You need to adjust the flame almost continuously. Try to keep it constant by keeping the flame medium low to medium high. Take out small balls out of the dough and roll out with rolling pin to make small circles. Cover with a damp kitchen towel and keep aside for 30 mins. For the Spice-n-Pepper flavored luchi: Add some salt, black pepper powder, white pepper powder, red chilli powder/chilli flakes along with a pinch of hing to the all purpose flour (maida).
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |