1)Design means It's a low level architecture ,You will come to know how classes interact with each other, Created and Destroyed. Pattern means Recommended solutions for recurring problems. 2)We already know frameworks already built in design patterns . But we know we feel more satisfaction . We know the pros and cons of that . 3)If you want to start learning design patterns ,Most preferred Book :: Head First Design Patterns.
The difference according to me in architecture and design is What and how What a system should do is defined in architecture and How it should do is Design
My 3 important takeaways are 1.Start learning patterns from Head first book, understand why they are used and explore frameworks in the language of your choice to understand how patterns are used and problems they solve 2. Simplicity is important while coding, use patterns only when needed 3. Use design principles like Single Responsibility, abstraction.
For me Architecture: is technical blue print of your business processes and culmination of teams. Design patterns: is just conventional pattern used to solve similar problems or recommendations for manageable code base
Expecting some thing on solid principles on class level, component level, module level and service or Microserive level how it changes and implementation at different level.
Spring boot is over engineered framework with bloated AOP. Too much of AOP that code readability is a nightmare. I call this framework an anti pattern in this age of server less.
1)Design means It's a low level architecture ,You will come to know how classes interact with each other, Created and Destroyed. Pattern means Recommended solutions for recurring problems.
2)We already know frameworks already built in design patterns . But we know we feel more satisfaction . We know the pros and cons of that .
3)If you want to start learning design patterns ,Most preferred Book :: Head First Design Patterns.
Fantastic and breathtaking conversation. Hats off to the classic trio.
The difference according to me in architecture and design is What and how
What a system should do is defined in architecture and How it should do is Design
My 3 important takeaways are 1.Start learning patterns from Head first book, understand why they are used and explore frameworks in the language of your choice to understand how patterns are used and problems they solve 2. Simplicity is important while coding, use patterns only when needed 3. Use design principles like Single Responsibility, abstraction.
Really awesome conversation. You guys justified why one should learn design patterns at first place.
knowledge is power thumbs up for these guys
Great brains from my University of RUclips.
This was wonderful. 👍👍
Looking forward for Architectural patterns,👍
For me Architecture: is technical blue print of your business processes and culmination of teams. Design patterns: is just conventional pattern used to solve similar problems or recommendations for manageable code base
I just love these videos !!
Happiness overflowing.
Amazing information.
How to check performance of developer and how to improve it
Expecting some thing on solid principles on class level, component level, module level and service or Microserive level how it changes and implementation at different level.
Can you some recommend design pattern books or resources for javascript developer ?
I don't see this being practiced in our daily work environment. Not sure of the reason.
Which book/course/ resources i should use to learn design patterns?
Head First Design Patterns.
Dive into Design Patterns by Alexander shvets. It's easy to understand.
Do people seriously use JDBC in Enterprise level? Would not it be easy to use wrappers instead of using JDBC?
What is the book mentioned about J2EE patterns?
Expert One-on-One J2EE Development without EJB
Spring boot is over engineered framework with bloated AOP. Too much of AOP that code readability is a nightmare. I call this framework an anti pattern in this age of server less.
Nah Spring boot ain't that hard dude. In fact it is easy once you get the hang of it.
Don't say like, like a thousand times.. This video will be lot better without those
I would like to say that I don't want to use like. But as you see, I like to use like a number of times.