Could you please recommend a book on Event Driven Architecture?

Great explanation

Thank u so much for saving my neurons from those lectures that make absolute zero sense. People on youtube be really saving lives!!

Great explanation. Very helpful as a new beginner. Here's another interesting AVENGERS video on SOLID Principles. Hoping it helps someone. kzbin.info/www/bejne/i3fWmWunfsZqjpo

damn your spitting a lot xD the sound Pt Pt Pt aaaaa

Thank you so much. The leanest explaination of SOLID I’ve ever learned from

3:54 Good Video but in object oriented the static variables dont go into the heap. zero-initialized static data goes in bbs and non-zero-initialized data goes in data <3

You can a and b not 6 and 7

to

What about having main (prod), dev (used for qa too) and feature branches (1 by dev feature) ?

"I noticed you're still working with polymers." The organization of "functions" is not the basis for logic. Functions should not be used to develop applications. Having billions of single-points-of-failures is not a technology. We should not be programming using a set of (just) hardware instructions grouped in a small number of statements as: functions, subroutines, macros, methods, event handlers, interrupts, message handlers, classes, etc.. Think of ways to not use "functions". It can be done.

thank you for this video

also good for networked games

thanks

Like many videos and books on design patterns, this videos also fails to meet the most desired objective - to help developers choose the right design pattern when certain situations are presented to them. The fancy names of the patterns and their explanation is great, but if developers are not able to analyze a problem and quickly "map" it to one of these patterns, then it isn't really useful.

Thanks for the video. In .NET we have one extension method in service class to add single instance of the class(AddSingleton). Do we still need to use singleton design pattern?

came for shift

Yeah but how do you create a new test?

**Summary: Monolithic vs Microservice Architectures** 1. Monolithic Architecture - All functionalities reside within a single codebase or project. - Simpler to develop and maintain initially, as it involves managing just one "component." - Internal communication is seamless, eliminating performance concerns between functionalities. - Challenges arise as the application grows: - Larger, more complex deployments. - Scaling issues: the entire application must scale, even if only one feature demands it. - Longer development and release cycles due to tightly coupled components. 2. Microservice Architecture - The application is divided into independent, smaller services, each focusing on specific functionalities. - Advantages: - Independent maintenance, development, and scalability of components. - Greater flexibility to scale individual services based on demand. - Challenges: - Increased complexity in development, testing, and debugging, especially for multi-service environments. - Difficult to simulate the entire application locally. - Higher infrastructure costs for small-scale applications. Communication Between Microservices: 1. API (Synchronous): Direct communication between components, often via REST or GraphQL. 2. Message Broker (Asynchronous): Tools like RabbitMQ enable decoupled communication by passing messages between services. 3. **Service Mesh:** Ensures service discoverability, communication reliability, and monitoring across microservices.

oh wow, im using strategy + factory + facade pattern unknowingly when implementing AES cipher since its have ECB, GCM, and CBC

I believe this movie (Predestination 2014 ) explain the true meaning of recursion, 😂 😂

Hi Alex, thanks for the roadmap. This is very resourceful, and it's just reminded me that there's still so much to learn. I was writing an article about learning web development, I am going to add your video as a reference.

Great explanation as well as examples given for the application of bitwise operations

This is the stupidest most useless set of "principles" and I'm tired of people saying otherwise.

Thanks, this video really helped me out

That is fascinating that for the fibonachi series, recursion is less efficient, while quick sort is amazing.

God, Java has to be one of the most poorly designed, yet ubiquitous languages

Hello ALex. Please do you have a roadmap or the tools a junior/intermediate should know?

ok and now how SSDs and HDDs manage the data if they not using HEAP and STACK ?

Your solution wont work with race condition

Please stop swapping between explanation and your cam every single second.. we need to understand what you are talking about while watching the visuals..

try anytype instead of notion opensource, offline and self hosted

Thnaks man. I will check out the blog

thanks for the video. as a new programmer, the books analogy is great and helped me understand , but you could explain what is the meaning of static void Main(string[] args) and why this is relevant to the call stack, or what is a "call" exactly?

I want to be a backend engineer

thx

Please don't add background music to videos when teaching, it makes it harder to follow what you're trying to share. :(

Thank you so much!

Just found your channel... great info. I'm a founder (or want to be) and am trying to get up to speed on all the dev concepts I need to hire, lead, and if I need to do the code myself some times... thanks a bunch! Especially for the flow charts of concepts I need to learn you've done in other videos.

U re a life saver.... God bless u

hey Alex ! it was very great to find your videos on this topic ! so clear and easy . can i grant your permission to translate your videos in persian by my voice and re share them on a channel for persian people to use them?

The c# propaganda goes crazy

Recursion is a Better Way to Understand Recursion

Sir , does learning java for backend is worth it?

Thanks for this very great video. Your explanation and example are SUPERB!

The notion of so-called "design patterns" was inherent in even the most early functional languages, e,g. lisp, but they were called "expressions" whose function definitions might or might not contain other expressions! It's not rokit syance, and DEFINATELY not LATTER-DAY object-oriented pseudo-paradigm-ical mumbo-jumbo! Simples, as simple can be! (:-)

recursion is SO GODLY POWERFUL in the right cases

Very nice breakdown ❤

The fact that static variables are stored on the heap is a bit confusing to me. I saw that within a process there's 4 segments which are: code, data, stack heap ( registers also). And then many sources state that static and global variables land in the data segment and not the heap. It's most appreciated if you can clarify this point to me (or anyone in the comments), thank you.

GitHub pages came to my rescue so many times for personal projects. Thanks for explaining the actions 👍