To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/DecodedFrontend/. The first 200 of you will get 20% off Brilliant’s annual premium subscription.
Hello, Dmytro! Would you be interested to make a video about contentChild/Children? Not how it works, but where are appropriate applications in terms of frontend abstractions? What business use case are they best for? Thanks!
Last two videos are sooo good! Please, continue this series about patterns with examples from the source code (if there are some :))) Btw, really enjoying the Forms course, thanks!
It's so easy to find videos on basic Angular concepts, but so difficult to find ones that go deeper. I love your videos, they help pretty experienced developer to get better and better. Thank you for sharing your knowledge.
Use it wisely. Not every switch/case has to be refactored like in the video. Sometimes it might bring unnecessary complexity to your code without real benefits
Nice example of the strategy pattern. I would like to mention one more example of this pattern in JS world - ability to provide the comparison algorithm to the sort method of Array. The idea is the same - runtime definition of the algorithm that is used inside the main context.
Hi Dmytro. Could you, please, teach us micro-frontend. Especially, angular/module-federation? That would be cool. You're an expert in Angular and i'm sure your video about it will be very usefull
Also, since you are highly expertised, could you share us with your vision about the future of Angular? Will it reach the performance of React some day? What are they (Google) going to improve in future etc. I've read in Twitter that they are thinking about implementation of some sort of JSX-like syntax, maybe you know something interesting
Hello Dmytro, Can you please make a video about change detection in depth understanding with real time scenarios and usage? It would be better for us if you make it. Thanks in advance 🙏
Awesome stuff! SOLID and Design Patterns are 2 topics that are very underrated and even sometimes hated in frontend world (LOL). Very nice to see more attention on this stuff as in my opinion it's one of the most important things in most if not any software project (be it frontend or backend). You can easily replace algorithms if you have a good architecture but if you don't then you will be spending countless hours refactoring =)
Thank you for your feedback, Alex! Always reach and valuable feedback. I am agree that knowledge about design principles and patterns can drastically improve the code we write. Also, very often they just sound scary and difficult but in reality it is not :)
In 10 years working for enterprise clients with Angular I've never seen true OOP patterns employed on the front-end. It's always Functional Reactive Programming and classes are only used for Angular directives, pipes or services. You don't have a Product class but a product object that is stored in Redux for example. If you start mixing code paradigms you will break the codebase coherency which will do more harm than good. We generally try to reduce the cognitive complexity, not increase it.
To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/DecodedFrontend/. The first 200 of you will get 20% off Brilliant’s annual premium subscription.
Hello, Dmytro! Would you be interested to make a video about contentChild/Children? Not how it works, but where are appropriate applications in terms of frontend abstractions? What business use case are they best for?
Thanks!
great video and especially the cat that takes center stage at the beginning 😅
hi, thx for informative videos, please upload more about design patterns.
Last two videos are sooo good! Please, continue this series about patterns with examples from the source code (if there are some :)))
Btw, really enjoying the Forms course, thanks!
It's so easy to find videos on basic Angular concepts, but so difficult to find ones that go deeper. I love your videos, they help pretty experienced developer to get better and better. Thank you for sharing your knowledge.
Thanks
Wow, thank you so much!🙌🏻
I have switch statements in my code that determine behaviour and now I know how to manage this. Thanks very much.
Use it wisely. Not every switch/case has to be refactored like in the video. Sometimes it might bring unnecessary complexity to your code without real benefits
Wow that simple example was very helpful!! Great explanation. 👏
Glad that I could make this topic clearer ;)
Just awesome. Always learning new things in details from your videos.
great video! I suggest turning off minimap and even sidebar to have more screen size
Good hint, actually! Thank you 😊
these videos are freaking amazing, Dmytro! please keep it up!!
Simple, yet effective :D Love your videos
Need all the design pattern in angular
Instant like. Love your content
Thank you 😊
Why there isn't a love button. This video e just perfect and you learn a lot from it. Thank you
Again, as usual well explained.Thank you.
Thanks for another useful video, Dmytro)
My pleasure!
Brilliant as always, thank you 🙏🙏
Very good series, Thanks! :)
Great video. We need more screen time for the cat though 🤣
Your required was accepted 😁
thanx for your great job!
I love this kind of videos :D
Awesome! Thanks for the feedback ;)
Hi! You are the best. Thanks for your videos. Could be some about unit testing? or testing in angular? Thanks you!
creator of the nest js in the background 0:10
Haha :) Exactly!
Thanks. Great explanation!
Very good video as always ! ❤️
Thank you! 😃
I always learn a lot of new things from your videos)
Glad to hear that, Yurii :) Thanks for the feedback!
Nice example of the strategy pattern. I would like to mention one more example of this pattern in JS world - ability to provide the comparison algorithm to the sort method of Array. The idea is the same - runtime definition of the algorithm that is used inside the main context.
Wow, amazing video!! 🚀
Which resources do u recommend to learn/practice more about design patterns?
refactoring.guru - is an awesome source to read more about it
Thanks a lot😃
Thanks, very great example, made me grasp the concept much easier.
Can you please do more videos revealing angular internals, and how they work
Thanks for this video dear friend!)
Great vídeo! Thank you!
Thanks. Pls explain how to understand the angular code.
9:48 rows 110, 111, 112, 113 - is that how overload implemented in TS?
Yes, exactly
How can you display the result at the end of console.log line?
Thank you
great video
Hi Dmytro. Could you, please, teach us micro-frontend. Especially, angular/module-federation? That would be cool. You're an expert in Angular and i'm sure your video about it will be very usefull
Also, since you are highly expertised, could you share us with your vision about the future of Angular? Will it reach the performance of React some day? What are they (Google) going to improve in future etc. I've read in Twitter that they are thinking about implementation of some sort of JSX-like syntax, maybe you know something interesting
Curretnly, people are hyped on Angular's Signal. Would be cool to hear about that.
Cool pretty useful
Hello Dmytro, Can you please make a video about change detection in depth understanding with real time scenarios and usage? It would be better for us if you make it. Thanks in advance 🙏
Hi Decoded Frontend, Is there any way to add open graph tags on angular, if it's rendered client side? Any suggestions would be great!!
awesome
Amazing
Awesome stuff!
SOLID and Design Patterns are 2 topics that are very underrated and even sometimes hated in frontend world (LOL).
Very nice to see more attention on this stuff as in my opinion it's one of the most important things in most if not any software project (be it frontend or backend).
You can easily replace algorithms if you have a good architecture but if you don't then you will be spending countless hours refactoring =)
Thank you for your feedback, Alex! Always reach and valuable feedback. I am agree that knowledge about design principles and patterns can drastically improve the code we write. Also, very often they just sound scary and difficult but in reality it is not :)
In 10 years working for enterprise clients with Angular I've never seen true OOP patterns employed on the front-end. It's always Functional Reactive Programming and classes are only used for Angular directives, pipes or services. You don't have a Product class but a product object that is stored in Redux for example. If you start mixing code paradigms you will break the codebase coherency which will do more harm than good. We generally try to reduce the cognitive complexity, not increase it.
Can you add the video to playlist about design patterns? :D
But it should be already there… 🤔 ok, I will check one more time
I can see it now, thank you :)
Did you change the flat ?
No, I changed a room :)
awsome
Дякую😊
Дуже дякую за фідбек 😊
Top
I see u fixed the thumbnail 😉
Yes :)
CEO was checking the class and how was the last feature you were assigned, he looks angry
Yeah, I probably forgot to food her, so that's why she looks angry :D
I'm looking for a job
Thanks. Great explanation as usual!
thanx for your great job!