Sudhansu Ranjan Dash’s Post

https://lnkd.in/d-VM373J new sessions is going to start on design patterns

I really like design patterns. You can use them to not reinvent the wheel and make your code simpler and more understandable. For me one of the most interesting is 'Observable', I remember using them, before people even named them. And you ? Which design pattern do you like or use the most?

Design Patterns greatly increases the flexibility of your program. Simultaneously, it provides a shared vocabulary for developers to communicate and convey the ideas. A pattern I often use is Strategy Pattern. It encapsulates the algorithms, makes them interchangeable and lets the algorithm vary independently from the clients that use it. Once you know the patterns, you start to spot the areas which can benefit by their usage.

In Continuation of Design Pattern Series, After the "Why Design Patterns", here we are with next topic "What are Design Patterns?" When the conventional approaches don’t work, you know it’s time to craft new solutions. This is what software development is all about, changing your current, ineffective ways to come up with more effective approaches. Let’s look at the problems we encountered. In inheritance, you added a new functionality, but in the process, you also changed the existing ones. The boats that weren’t supposed to dive suddenly find themselves inheriting the dive() method. Using an interface did seem to solve the problem but it introduced new issues. For every class needing the new feature, you had to implement the dive() method. If there’s even a small change in the feature, you’ll need to make the change across all the classes implementing the method. According to design principles, when you have got some code that is a new requirement, the behavior needs to be encapsulated and kept separate from the existing code so that it doesn’t lead to unexpected consequences. This principle serves as a foundation for many design patterns, some of which, you will see in the next post. You will also look at the design pattern used to solve the above problem. Thanks For Reading..!

https://lnkd.in/gSEsVgtP State design patterns. seperate logic from implementation with same set of methods

https://lnkd.in/g4UhY7vk State design patterns. seperate logic from implementation with same set of methods

🚀 Celebrating Agile, Scalable, and Well-Tested Code with Outstanding Product Management 🖥️💡 A huge shoutout to an incredible enterprise development team for delivering agile, scalable, and robustly tested code! 🙌 But none of this would be possible without the exemplary work from their product management team in delivering clear, detailed specs that set them up for success. In today’s fast-evolving tech landscape, writing scalable and well-tested code is no easy feat. With well-crafted specs, their teams can move efficiently and confidently, knowing they're building the right solution. Their product management team has consistently provided the roadmap for success, ensuring their vision aligns with business needs and customer expectations. 🌟 Why does this matter? Agile frameworks mean they can adapt swiftly, delivering features faster without compromising on quality. Scalable code ensures their solutions grow with our business, supporting more users, more data, and more complexity. Thorough testing guarantees reliability, preventing costly errors and enabling smooth, uninterrupted services. Excellent specs from product management provide clarity, focus, and alignment, helping the dev team hit the mark every time. Kudos to both the development and product management teams for their collaboration, innovation, and commitment to excellence! 🚀 Let’s keep pushing boundaries and building the future, one sprint at a time. #AgileDevelopment #ScalableSolutions #TestedAndTrusted #ProductManagement #Teamwork #EnterpriseTech #QualityCode #SoftwareEngineering #ExcellenceInAction #chatgptftw

Don't use #designpatterns just because it sounds cool. There will be more harm than good if you don't aware of the problems you're trying to solve Here are some of the consequences - Over-engineering - Misapplication - Inflexibility - Hard-to-understand code - Adding more overhead of complexity - Performance Overhead. Make sure to only apply design patterns when you need them.

Summarising use case of Creational Design patterns.