The issue is, everyone in the dev world wants to leave a stamp, which is making a big mess with all these frameworks. I have always compared it to carpenters. They all have an opinion of how it should be done, but in the end, there is always an elegant approach and a standard to follow. This video is that, an elegant approach to explaining such a complex topic. Amazing work!
hi! sorry. i'm 2 minutes in and i feel strongly compelled to write this. i appreciate the very concept of this video. i think it is very noble of you to be generously sharing your knowledge to help beginners understand something that can get quite big and intricate and overwhelming. i appreciate that very, very much. thanks.
Thanks so much! I'm still getting my "feet on solid ground" so to speak with all of this and your big picture framework/IKEA store analogy has helped a lot!
Wow, this tutorial is excellent! The step-by-step explanation and clear demonstrations really helped me grasp the concepts easily. Thank you for creating such valuable content!
OMG ... I don't know, how should I thank him. I can bet, you won't find best explained tutorial other than this. Hats off and thanks a lot for fun explaination. Enjoyed every min of it.
watching this in 2023 handsoff to your work guy like me without any prior experience to things could understand the things how they are working no words sir i d love to see your work more
This is verrrrrry rich content ,thank u sir for your effort and if its subscriptions you are looking for ,I guess people haven't bumped to this yet but theyr surely coming.
Wow !!! No words to thank him ! enlightening experience .. He just summarized the whole vast stack of technologies in a simplified understandable context . Thank you very much coding Sensei !
Sensi, you are the savior, I had many questions about the software technologies, why do we use this and that and asked many real software developers, none gave me such a clear view as you, thank you for your teaching efforts🙏
Add 'thank💰' feature sir . This is a Great Great Great Great video sir ! I have been searching on this topic (big picture) fr months and sadly this video didn't show up in search feed . Ig u have to promote this video more. Bcs this is a gem 💎
Thanks much Sensei. This is the perfect way of teaching. I love it. Please post more about servers and web application apache configuration setup from scratch. Please continue posting like this. Thanks
Hello Sensei, thank you for your wonderful explanation, I'm into PO role, which is not completely technical but on daily basis I have to interact with my Dev team. Your video is really helpful to get the details Can you make more such videos for non technical people to understand how Front end, back end interacts, role of API services, how UI dev fetch the info from Backend and process it to UI , and some more. Thank you
Great video, thanks for sharing! Wanted to ask a few questions just to make sure I have understood the analogy correctly: 1. If the receptionists are Web servers, who is the DNS server? Are they the same thing? 2. The DNS server finds a location in "its own directory" and fetches information from that address; in this case what exactly is the IKEA worker? Is it the IP address found by the DNS server? 3. If the workers and inventory managers speak different languages, how to they communicate with each other? What is the analogous of the inventory worker when I'm trying to access a web app?
Hi Eshan. 1) They are not the same thing. DNS server is like a phone directory of homes. Receptionists are those who welcome guests to the house. 2) Workers are those who assemble furnitures or in the web world, the html/css/js. They do not talk directly to the DNS server as DNS server sends the request to the appropriate house and within the house, the receptionist takes the order. The workers only talk to the receptionist and not the DNS server. 3) Inventory workers are database engines (SQL, MongoDB, etc). The workers usually only talk within their own language. When you later build several applications (e.g. micro-service architecture), where each application is built in a single language, you can have these "services" talk to each other using a common language such as XML, JSON, etc.
Great content... Lots of information. One suggestion, if visio or lucid chart kind of tools are used to explain the pictures, then it will improve the quality further
This video is excellent. The only place I disagree is here "People put so much emphasis on the programming language but you shouldn't". I definitely think people should care about the programming language...they are all different and they were made for different purposes. Coding a web app in Java to me doesn't make any sense! Especially when you have PHP...it was made for that! And forget about NodeJS...Don't kill me.
Sure, each language was made with a specific purpose in mind, but for the most part, no one is gonna use say, MatLab or Fortran to make a web app, theyre going to use a language that can make a web app, so it doesnt matter what web app language you use, just as long as yoh make it good, because I use Go to make my web apps, but the web is 80% PHP, theres also alot of JS and Python web apps, sometimes multiple languages are used, but they all work so it doesnt matter
