Introducing levonog, your hub for computer science content on RU-vid! Led by a dedicated creator, this channel is your one-stop destination for all things coding-related. levonog brings you concise and informative videos that cover a wide range of topics. From beginner-friendly tutorials to advanced techniques, these videos are designed to help you level up your coding skills. But that's not all! levonog also dives into the broader realm of computer science, offering videos on various topics like design patterns, algorithms, data structures, software engineering, and more. Whether you're a student, a professional developer, or simply curious about the world of coding, there's something here for everyone. Subscribe to levonog now and unlock a world of endless possibilities in computer science and beyond!
Hi! Really love your videos, very understandable and nice to watch. I think that in this example a removePartN() group of methods should be added to the builder interface, otherwise it would be impossible to remove products form a pizza after being added, or am I missing something?
It's apparent early on that understanding interfaces is key, crucial, paramount and fundamental to implementing design patterns. Interfaces are at the heart of being good at designing software
Hello! Strategy is a different pattern, it helps to have a family of interchangeable algorithms. You can watch the video on the channel about the Strategy pattern :)
Great video! can we get an in-depth series for each design pattern? with examples of before and after code, refactoring, and combining one or more design pattern for each solution.
This course took me 8 months and right now I want to take a break from design patterns and concentrate on system design, but who knows, maybe in the future :)
Yeah, you can’t do this if you don’t want to use all the enums. But there are other solutions, for example, you can create another enum, or you can use Extract built-in type to extract needed enums.
Kudos on the really high-quality presentation, though tbh we don't really need a specific OO design pattern for creating a set of stages. This is more of a specific implementation for a use case than a design pattern. It can probably be naturally created by a developer who's thinking about requirements like going to the next or previous stage, or jumping to a specific stage.
Yes of course, this example is for demonstration purposes only. I felt that this example was the best way I could tell about this design pattern, so I chose it. BTW, thanks for the comment, really appreciate it!
This is excellent, I got a lot out of this! Look forward to exploring more. Gladly subscribed - hoping the RU-vid algorithm will serve up your work to many as it did to me two minutes ago 😊
