That turned into an axcellent explanation! I wish I had came here earlier so I wouldn't had so much struggle with this topic, yet you made it even clearer.

Appreciate it

top tier explanation

perfect, but I think you got a little bit lost with unnecessary code refactoring

In the second example with the 'static' keyword, it seems to me that when LongLivedLeak() finishes execution, unless 'instance' is stored elsewhere in the program (like returning it or it is assigned elsewhere to a variable outside the function), then 'instance' would essentially be garbage collected due to the function going out of scope when it is done. I can see 'instance' not being garbage collect if that instance was assigned elsewhere and never handled with properly.

excelent video

great video Mark!

Thanks so much! Your tutorial is the best. It's super clear and to the point. Nice work!

Exactly the kind of explanation I needed, thank you Mark

Great video, thanks for sharing!! do you have more material? greetings.

Hey Mark, do u even know a component that is also able to grab the styles, layouts, breaks, images? I created a letter with html but I lose everything except of the text. But I will try that html2pdf converter- thx mate 😊

Excellent, really helped. Thanks!

I like your channel. I always learn new things.

Thank you, saved me! 🙏

Nice one! I think you should make an another video about threads and multi-threads, That video would be complementary and relevant resource with this video. Thanks again!

🔥🔥🔥

So sad that discovered your channel this late, but this helps me learn a lot after tons of struggle. Definitely one of the most underrated coding channels I've ever saw keep it up!.

top tier

Great explanation 💯

Thanks, really good video! Only one question more: is it possible to show the selected item with another css style?

0:43 `grid[1, 2] = 5;` - something looks really fishy here :)

Great high level overview of what a state machine is.

Super helpful as a long-time engineer who needs to brush back up on C# again. I'm finding it's getting harder as I get older to keep up with stuff, maybe I gotta pick up coffee again 😅

I think the Liskov Substitution Principle is probably one of the most misunderstood principles in programming. It's not about child classes, it's about class hierarchies and the idea is that you *can* have a class hierarchy when the child classes implement similar *behavior* as the parent class, otherwise you will eventually run into inheritance-related issues. Let's work a bit with this specific example: you have a Bird class with two children classes, Pigeon and Eagle. Since the fly behavior is common to both Pigeon and Eagle, you decide to put the method on the Bird class. But then the requirements change and you need to add a Penguin class, which cannot fly. One common solution is to create an inheritance tree, with a FlyingBird class that inherits from Bird and implements the fly method. Pigeon and Eagle will now inherit from the FlyingBird, while Penguin inherits from Bird. It's the *FlyingBird* class that's violating LSP and thus helps you avoid building a complex chain of inheritance. *That's* the value of the Liskov Substitution Principle.

Can it be used to extract information from pdf invoices \ cv's \ etc?

I 100% agree on everything. Good tier list

I would like that Unity can implements DI in a very friendly friend.

Great explanation :) Thanks!

I saw your comment in Travis media and came here, new subscriber

great video

Id love to see a tutorial where you put a demo wireframe together. Would be interesting to see the tools you use and your thought process.

Well explained video, many thanks.

Great explanation keep it up

Good idea, simple but useful

How do you get past all the 406 'unacceptable' errors when pushing the packages to the source?

Really well explained! Looking forward to your next video.

Do I detect a fellow South African accent ?

Useful video, thanks. I disagree with the last comment though, I think the presentation would have been better if planned and scripted because someone who was new to the subject would struggle to keep up when it's a bit all over the place.

Very powerful stuff! I like that you kept the unscripted stuff in the tutorial. Watching someone genuinely explain their thoughts is so much more entertaining. Keep them coming.

I am a beginner and your videos have helped me a lot. thank you very much

this was very helpful in preparation for my interview, thanks!

I am confused with the second example, is my understanding that the instance will be mark for collection after the function finish, as the variable that holds the pointer is in the stack.

Great video - is anybody able to consume your package (when they have your username & key)?

Great video! Didn`t know about the event listener example

Nice ✨️ 😊

Great video Information about Blazor. Thanks for sharing this. I think Blazor has a great future. Please continue

So for the GitHub user name you used..... that will be committed and used by other developers? I wonder if making a Packages user in GitHub and maybe use that universally. ??

I take issue with the idea that Domain Models, Entities, or Models are just simple objects that mirror database records. Ideally, the business layer should be blissfully unaware of the underlying database. It’s the infrastructure layer’s job to translate these Models/Entities into database records. Sure, for small or even medium applications with straightforward CRUD operations, this overlap might seem true. But when business requirements get more complex, we often need sophisticated data structures to represent a single business element. These structures can’t always be squeezed into a single database record.

In all my teams over the last n-years, "infrastructure" always means cloud resources.

Was literally looking for information on this topic. Great video quality man! Keep up the good work and looking forward to seeing more blazor uploads!