Episode 21 - Design Pattern 1

Sep 21, 2019Download as PPTX, PDF1 like11,683 views

The document provides an overview of design patterns and principles for software development. It discusses the SOLID principles of open/closed, single responsibility, Liskov substitution, interface segregation and dependency inversion. It defines design patterns as common solutions to recurring problems in software design. The Gang of Four are introduced as authors of a seminal book on design patterns, categorizing 23 patterns into creational, structural and behavioral groups. The session concludes with soliciting questions and announcing the next topic.

Path to Code
Begin Your Salesforce Coding Adventure

Jitendra Zaa
Salesforce MVP
Sr Technical Architect
23x Certified
@Jitendra Zaa
Speaker

Agenda
• SOLID
• Design Principles
• What are design Patterns
• Who are Gang Of Four
• GoF Patterns
• Creational Pattern
• Example

Some House Rules
• Please mute your mic
• Keep adding questions in Zoom Q&A Window
• No question is too small
• Questions will be answered in last 15 mins

Open Closed Principle
Class should be Open for extension but Closed for Modification.

Example
Create a Program to accept Circle and Square Object and return Sum of
their Area.

Change in Requirement
Add Support for Rectangle Also. What
would you do ?
Add one more If else? That would be
breaking Open Closed Principle. Class should
be closed to modification but open to
Extension.

Solution
Add Interface so that all Shape
should follow that interface, new
Class will become

Single Responsibility Principle
A class should have one and only one reason to change that means
only one job.

Question
AreaCalculator class calculates area and returns result of sum of area
of all Shapes.
How to add functionality if we want to get area result as JSON or HTML
?

Explanation
Its breaking Single Responsibility Principle. AreaCalculator should only
change if formula related to Area changes

Liskov Substitution Principle
If class B is a child of class A, then A can be replaced by B, without
changing anything in a program. In other words, the LSP principle
states that you should not encounter unexpected results if child
(derived) classes are used instead of parent classes.

Interface Segregation Principle
This states that do not force a child class to depend on a method that is
not used for them. This principle suggests that you break interfaces
into smaller ones so that a client can only implement an interface that
is of interest.

Dependency Inversion Principle
This states that modules should not depend on each other directly and
should depend via an interface (abstraction).

What are Design Patterns ?
Each Pattern describes
1. A problem which occurs again and again
2. A core of the Solution
3. Consequences of Solution

Design Patterns Does not
Provide Actual Implementation Details

Who are Gang of Fours
Book written in 1994 consist of 23 Design
patterns by
1. Erich Gamma
2. Richard Helm
3. Ralph Johnson
4. John Vlissides

Gang of Four Patterns
Creational Patterns Structural Behavioral
1. Abstract Factory 6. Adapter 13. Chain of responsibility
2. Builder 7. Bridge 14. Command
3. Factory Method 8. Composite 15. Intercepter
4. Prototype 9. Decorator 16. Iterator
5. Singleton 10. Facade 17. Mediator
11. Fly Weight 18. Memento
12. Proxy 19. Observer
20. State
21. Strategy
22. Template Method
23. Visitor

Reference
• Apex Design Patterns
• SOLID Principle

This document provides an overview of key object-oriented programming concepts in Salesforce including classes, objects, inheritance, abstract classes, and interfaces. It discusses how classes define objects, how to instantiate objects, access specifiers, static methods, inheritance which allows extending existing classes, abstract classes which define common methods, and interfaces which enforce method signatures. Code examples are provided to demonstrate these concepts. The document also recommends books for learning Apex at different skill levels and includes an agenda and rules for the session.

Episode 5 - Writing unit tests in SalesforceJitendra Zaa

The document provides an agenda for a session on writing unit tests in Apex. It discusses why unit tests are important in Apex, how to structure test classes, best practices for testing, and resources for learning more about Apex testing. The session demonstrates executing unit tests and techniques like accessing private members, running tests within limits, and creating test data. Attendees are encouraged to ask questions during the last 15 minutes.

Episode 23 - Design Pattern 3Jitendra Zaa

This document discusses a design pattern called the Facade Pattern. It summarizes that the Facade Pattern encapsulates complex systems and provides a simpler interface. It gives an example where a facade pattern is used to handle a credit card transaction in a standardized way without changing existing code. It then discusses how the Strategy Pattern could be used to support different payment types like debit cards or PayPal by deciding the payment algorithm at runtime. The document ends with announcing the next episode will be an open Q&A.

Episode 1 - PathToCode.comJitendra Zaa

This document provides an overview and introduction to coding in Salesforce, including why coding is needed, the developer console, naming conventions, data types, collections, pass by value vs reference, and Trailhead modules to get started. It discusses primitive data types like Boolean, Date, Decimal, and String, as well as collections like Lists, Maps, and Sets. It also covers naming conventions like camel case and pascal case.

Episode 20 - Trigger Frameworks in SalesforceJitendra Zaa

This document discusses trigger frameworks in Salesforce and their benefits. It provides an overview of trigger execution order and common patterns for writing trigger frameworks, including the trigger handler and interface-based patterns. The document demonstrates examples using these patterns. Trigger frameworks provide benefits like consistent execution, preventing recursion, improved testability and maintainability. Choosing the right framework depends on factors like complexity, extensibility and code reusability. Resources for learning more about trigger frameworks are also provided.

Episode 22 - Design Pattern 2Jitendra Zaa

This document summarizes a presentation on design patterns in Salesforce development. It discusses the Singleton and Factory Method creational design patterns. It provides code examples demonstrating how to implement these patterns to solve common problems like automatically populating a field based on another field. It also discusses how to choose design patterns to optimize performance by reducing queries. The presentation concludes with reminding attendees of the next session and thanking them for their time.

Episode 18 - Asynchronous ApexJitendra Zaa

This document discusses asynchronous Apex in Salesforce, including future methods and queueable Apex. It provides an overview of asynchronous Apex, why it is used, different asynchronous Apex approaches, and compares future methods and queueable Apex. The agenda includes explaining asynchronous Apex, reasons for using it like avoiding governor limits and allowing callouts from triggers, asynchronous governor limits, future methods, queueable Apex, and a demo.

Making a Mock by Kelsey ShannahanQA or the Highway

Testing within a closed system is easy. Everything is generally accessible and can be interacted with freely. But what happens when the application requires integration with one or more third parties in order to function? In unit tests, we can use mocks and there are many Ruby libraries to make that happen. However, this doesn’t help us much when we’re testing deployed code in end-to-end scenarios or exploratory tests. The solution I found was to build a mock application to mimic the third party. This talk will cover the process and tools used to build the application, the advantages/disadvantages it provides, and explain how this mock is utilized in real-world situations.

Improving Test Team Throughput via Architecture by Dustin WilliamsQA or the Highway

A lot of modern testing teams are built from people with some automation experience, developers, and people who think code is something used to open a safe. These diverse backgrounds bring a diverse set of ideas, but don’t always find optimal division of work. With some fairly small changes in automated test design, we can leverage the best skills of all team members to not only improve throughput, but to end up with a better overall product. These design principles help isolate truly challenging code problems and help separate the concerns of test structure and test execution. If your team has ever said (with sad faces) “We’re still automating that”, then come discover how tomorrow you can exclaim “That’s Done!”

Agile testingandautomationjeisner

1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important. 2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews. 3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.

Introduction to Test Driven DevelopmentSarah Dutkiewicz

Being Lean Agileprakashmpujar

The core idea of lean is to eliminate/reduce non-value-added activities (termed "wastes") and thus increase customer value. The Agile itself is a lean for the software development life cycle, and I am sharing a couple of Agile best practices adopted by my teams to make the Scrum methodology more extra lean. The presentation contains the best agile practices and their benefits in terms of Lean in an agile methodologies

Sustainable Automation Frameworks by Kelsey ShannahanQA or the Highway

The document discusses sustainable automation frameworks for testing software. It addresses common problems such as hardcoding tests, having too many step definitions, and poor data management. The proposed solutions include using a page object model to organize test code, standardizing step definitions to represent business logic at a higher level, and having a consistent way to load and reuse test data. Maintaining an organized framework is emphasized as important for allowing tests to run quickly and changes to be made easily.

Code reviewAleksey Solntsev

This document discusses how to improve software quality through code reviews. It begins by stating the goals of code review, such as improving code quality, sharing knowledge, and educating developers. It then discusses classification of code reviews from less to more formal. The document outlines some best practices for code reviews, including having a reviewer and author, choosing reviewers strategically, and driving the review in different ways. It provides answers to common questions about organizing effective code reviews and leaves with tips, such as tracking reviewers, using checklists, and ensuring comfortable conditions for all.

Continuous delivery test strategiesHylke Stapersma

XP InjectionAleksey Solntsev

Continuous business goal validationHylke Stapersma

How to be proud when you are doneAleksey Solntsev

Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server. So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.

Entity Framework: To the Unit of Work Design Pattern and BeyondSteve Westgarth

The document discusses issues with traditional ASP.NET application architectures and how the introduction of MVC helped address some problems. It then describes how the presenter implemented the Unit of Work pattern to help with testing and database consistency in their application. However, this implementation violated SOLID principles. The presenter improved the design by separating concerns into distinct layers and implementing generic repositories. This made the code more testable and decoupled from Entity Framework while better adhering to object-oriented design principles. In the end, the presenter advocates evaluating design patterns critically and continuously challenging accepted approaches.

Teamleader testcon 2019Thomas Noë

Testers, do you find yourself still siloed even after breaking down the “walls” between development and testing? Are you in a hole of never-ending test creation and maintenance, removing you from focusing on user experience? Does ad-hoc exploratory testing still happen because your tests aren’t stable enough to test the app before it gets to production? When your team starts to adopt agile and DevOps development practices, how do you scale testing to keep up with higher release frequencies? Test automation is a big part of the solution. But beware that you’re doing it the wrong way. In this talk I will explain how to reverse the negative impacts brought about from common – but not necessarily “good” – practices around automation tooling and QA hiring practices. I will talk about what changes you need to make to win back more time to develop and implement your test strategy. I will elevate your testing strategy from “surviving” to “thriving” in DevOps.

Few minutes To better Code - RefactoringDiaa Al-Salehi

TDD Basics with Angular.js and JasmineLuis Sánchez Castellanos

The document discusses Test-Driven Development (TDD). Some key points: - TDD involves writing automated tests before writing code to ensure tests fail initially and then passing the tests by writing just enough code. This prevents writing extra code and helps design code structure. - TDD provides benefits like confidence in code quality, catching errors early, and giving feedback on changes. Unit tests should initially fail, test individual components, and not be for finding bugs which is done through manual testing. - The basic TDD process is to create a failing test, write just enough code to pass the test, refactor code, and repeat the process for each new feature or change. This helps integrate TDD into

Scala Days Chicago 2017: Building a Company on ScalaNatalie Vegel

An Introduction to Unit TestingSahar Nofal

Unit testing involves writing automated tests to test code. Automated tests are repeatable and help catch bugs before deploying code. The main benefits of unit testing are that it allows developers to test code frequently and in less time, catch bugs before deploying, deploy with confidence, reduce bugs in production, and refactor code with confidence. There are different types of tests including unit tests, integration tests, and end-to-end tests. Unit tests isolate a unit of code without external dependencies and execute fast but provide less confidence. Integration tests involve external dependencies and provide more confidence but take longer. End-to-end tests drive the application through its UI and provide great confidence but are slow. Good unit tests

Presentation_TDDRaihan Masud

TDD is a process where test code is written before or alongside production code to drive the design and development of a project. It involves writing automated unit tests to force decoupling of dependencies and provide comprehensive testing. TDD helps think through requirements and design before coding to catch early bugs. It is an incremental process where tests are written and run continuously to build confidence with each new feature added. The key steps are to write a test, make it compile even if it fails, run it to failure, implement the code to pass the test, then refactor and repeat the process.

Benefits from AATsWyn B. Van Devanter

Quality not-speed-for-distrobutionbownyboy

The document argues that agile practices prioritize quality over speed, which ultimately leads to faster delivery. It provides reasons for using practices like user stories, planning, continuous integration, testing, and code reviews: they catch bugs early and prevent wasted time on substandard or wrong software. While these practices take time up front, they save significantly more time than fixing issues late in a project, leading to higher quality and value delivered to customers. The document asserts that high quality projects complete more quickly due to fewer bugs and reworks.

What is this agile thing anywayLisa Van Gelder

The document discusses various concepts and practices related to agile software development, including: - The agile manifesto which emphasizes individuals, working software, customer collaboration, and responding to change. - Core agile concepts like short iterations, planning one iteration at a time, frequent code releases and customer feedback. - Specific agile frameworks like eXtreme Programming (XP), Scrum, and Kanban/Lean. - Testing approaches like unit tests, integration/acceptance tests, test-driven development (TDD), and behavior-driven development (BDD). - Other practices like continuous integration, domain-driven design (DDD), and DevOps which emphasize collaboration between developers and operations

Soild principlesAvidnyat Chiddarwar

Design Principles to design PatternsFaizan Haider

More Related Content

What's hot (20)

Improving Test Team Throughput via Architecture by Dustin WilliamsQA or the Highway

Agile testingandautomationjeisner

Introduction to Test Driven DevelopmentSarah Dutkiewicz

Being Lean Agileprakashmpujar

Sustainable Automation Frameworks by Kelsey ShannahanQA or the Highway

Code reviewAleksey Solntsev

Continuous delivery test strategiesHylke Stapersma

XP InjectionAleksey Solntsev

Continuous business goal validationHylke Stapersma

How to be proud when you are doneAleksey Solntsev

Entity Framework: To the Unit of Work Design Pattern and BeyondSteve Westgarth

Teamleader testcon 2019Thomas Noë

Few minutes To better Code - RefactoringDiaa Al-Salehi

TDD Basics with Angular.js and JasmineLuis Sánchez Castellanos

Scala Days Chicago 2017: Building a Company on ScalaNatalie Vegel

An Introduction to Unit TestingSahar Nofal

Presentation_TDDRaihan Masud

Benefits from AATsWyn B. Van Devanter

Quality not-speed-for-distrobutionbownyboy

What is this agile thing anywayLisa Van Gelder

Improving Test Team Throughput via Architecture by Dustin WilliamsQA or the Highway

Agile testingandautomationjeisner

Introduction to Test Driven DevelopmentSarah Dutkiewicz

Being Lean Agileprakashmpujar

Sustainable Automation Frameworks by Kelsey ShannahanQA or the Highway

Code reviewAleksey Solntsev

Continuous delivery test strategiesHylke Stapersma

XP InjectionAleksey Solntsev

Continuous business goal validationHylke Stapersma

How to be proud when you are doneAleksey Solntsev

Entity Framework: To the Unit of Work Design Pattern and BeyondSteve Westgarth

Teamleader testcon 2019Thomas Noë

Few minutes To better Code - RefactoringDiaa Al-Salehi

TDD Basics with Angular.js and JasmineLuis Sánchez Castellanos

Scala Days Chicago 2017: Building a Company on ScalaNatalie Vegel

An Introduction to Unit TestingSahar Nofal

Presentation_TDDRaihan Masud

Benefits from AATsWyn B. Van Devanter

Quality not-speed-for-distrobutionbownyboy

What is this agile thing anywayLisa Van Gelder

Similar to Episode 21 - Design Pattern 1 (20)

Soild principlesAvidnyat Chiddarwar

Design Principles to design PatternsFaizan Haider

SolidHadi Ehterami

The document discusses the SOLID principles of object-oriented design, which are a set of five design principles intended to make software designs more understandable, flexible and maintainable. It defines each principle: single responsibility, open/closed, Liskov substitution, interface segregation, and dependency inversion. Following these principles helps produce code that is less complex, more readable, extensible, maintainable and reusable with looser coupling between modules and better testability compared to code not following these principles.

DesignPrinciples-and-DesignPatternsBasavaraj Patil

The document discusses design principles, patterns, and GRASP patterns. It provides explanations of key principles such as SOLID principles, composite reuse principle, law of demeter, and others. It also explains important design patterns and GRASP patterns. Some key points: - Design principles like SOLID principles help avoid bad designs and guide developers to create designs that are flexible, understandable, and resilient to change. - GRASP patterns provide guidelines for assigning responsibilities to classes based on concepts like information expert, creator, and controller. - Design patterns are proven solutions to common programming problems that can be reused in different situations. Some patterns discussed are creational, structural, and behavioral patterns. - Applying the right

Applying design patternsYogeshwaranT

Design patterns became popular in the 1990s due to influential books describing recurring solutions to object-oriented design problems. A design pattern describes a general solution to a common problem in software design. They allow programmers to reuse successful past designs. Some key design patterns discussed include state, observer, open-closed principle, and dependency inversion. Applying design patterns helps increase design speed and reuse, while reducing costs.

GoF Design patterns I: Introduction + Structural PatternsSameh Deabes

This document discusses structural design patterns from the Gang of Four (GoF) patterns book. It introduces proxies, decorators, adapters, façades, and composites patterns. Proxies provide a placeholder for another object to control access. Decorators dynamically add/remove responsibilities to objects. Adapters allow incompatible interfaces to work together. Façades provide a simplified interface to a subsystem. Composites represent part-whole hierarchies to access all parts uniformly. Bridge and flyweight patterns were not covered due to dependencies on other patterns. The document emphasizes introducing extra levels of indirection to solve problems and favoring composition over inheritance.

Design principle vs design patternsPrabhakar Sharma

Oop principlesMd. Mahedee Hasan

The document provides an introduction to object oriented design principles with C#. It discusses the SOLID principles, which are single responsibility principle (SRP), open-closed principle (OCP), Liskov substitution principle (LSP), interface segregation principle (ISP) and dependency inversion principle (DIP). For each principle, it provides a definition, real world example and demonstration of implementation. It also discusses other design principles like program to interface, dependency injection and composition over inheritance. The document is intended to help understand and apply good object oriented design in software projects.

Refactoring, Therapeutic Attitude to Programming.Amin Shahnazari

This document discusses refactoring and common programming diseases. It begins with an introduction to refactoring, defining it as improving the design of existing code without changing its external behavior. It then discusses reasons for refactoring like improving code understandability and design. It also discusses when refactoring should occur, such as when adding new features or fixing bugs. The document then covers common programming diseases called "code smells" including bloated code, object-oriented abuses, redundancies, and couplings. It provides examples and treatments for each smell type.

Software design principlesMd.Mojibul Hoque

The document discusses various software design principles and guidelines for creating maintainable and extensible software. It covers principles like high cohesion and loose coupling, the Single Responsibility Principle, Open-Closed Principle, Liskov Substitution Principle, and others. It also discusses symptoms of deteriorating design like rigidity, fragility, immobility and viscosity. Overall, the document provides an overview of fundamental object-oriented and Unix-based design principles for crafting software that is simple, robust and flexible.

Single Responsibility PrincipleBADR

The OO Design PrinciplesSteve Zhang

The document discusses several object-oriented (OO) design principles including the single responsibility principle (SRP), open-closed principle (OCP), Liskov substitution principle (LSP), interface segregation principle (ISP), and dependency inversion principle (DIP). It also discusses design patterns, refactoring, and design by contract (DBC) as ways to prevent software decay over time and improve design quality. The key OO principles guide developers to create flexible, maintainable and reusable software designs.

Software Design Principles and Best Practices - Satyajit DeyCefalo

The document discusses software design principles and best practices, including definitions of technical debt, stakeholders' goals, causes of technical debt, types of technical debt, code smells, common code smells like comments, uncommunicative names, long methods, and design principles like SOLID principles. It provides examples of single responsibility principle, open-closed principle, Liskov substitution principle, interface segregation principle, and dependency inversion principle. It emphasizes that good code is readable and maintainable by other programmers.

Solid principlesKumaresh Chandra Baruri

How to Master Development's Solid Principles | Tutort AcademyTutort Academy

Design Patterns .NetHariom Shah

This document discusses design patterns, including the Gang of Four (GoF) patterns. It provides an overview of creational design patterns like Singleton, Factory Method, Abstract Factory, and Builder patterns. For each pattern, it describes the intent, participants, structure, and examples of how they are used in the .NET framework. It also discusses principles of object-oriented design like encapsulation, inheritance, and loose coupling. The document is intended to teach developers about design patterns and how to apply them.

12266422.pptCSEC5

The document discusses design patterns and the Gang of Four (GoF) patterns. It provides an overview of the different types of patterns including creational, structural, and behavioral patterns. It then focuses on the Adapter pattern, describing its problem of resolving incompatible interfaces, its solution of using an adapter to convert one interface to another, and provides an example of how an point-of-sale system may need to adapt different third-party services that each have different APIs.

Software design principles - jinal desaijinaldesailive

Clean Code - Part 2Knoldus Inc.

android principle.pptxdebasish duarah

Soild principlesAvidnyat Chiddarwar

Design Principles to design PatternsFaizan Haider

SolidHadi Ehterami

DesignPrinciples-and-DesignPatternsBasavaraj Patil

Applying design patternsYogeshwaranT

GoF Design patterns I: Introduction + Structural PatternsSameh Deabes

Design principle vs design patternsPrabhakar Sharma

Oop principlesMd. Mahedee Hasan

Refactoring, Therapeutic Attitude to Programming.Amin Shahnazari

Software design principlesMd.Mojibul Hoque

Single Responsibility PrincipleBADR

The OO Design PrinciplesSteve Zhang

Software Design Principles and Best Practices - Satyajit DeyCefalo

Solid principlesKumaresh Chandra Baruri

How to Master Development's Solid Principles | Tutort AcademyTutort Academy

Design Patterns .NetHariom Shah

12266422.pptCSEC5

Software design principles - jinal desaijinaldesailive

Clean Code - Part 2Knoldus Inc.

android principle.pptxdebasish duarah

More from Jitendra Zaa (20)

Episode 13 - Advanced Apex TriggersJitendra Zaa

The document discusses implementing advanced triggers in Apex using a trigger handler pattern. It begins with an agenda that includes challenges with triggers, trigger patterns, anatomy of a handler pattern, implementing an advanced pattern, and order of execution. It then discusses challenges like maintenance, non-deterministic execution, and infinite loops. The handler pattern is presented as a solution that enforces best practices, promotes clean code and reusability, and prevents issues. A demo is provided of implementing the pattern. Resources on triggers, patterns, and order of execution are listed along with Trailhead modules on the topic.

Episode 15 - Basics of JavascriptJitendra Zaa

This document provides an overview and agenda for a session on JavaScript basics. It introduces concepts like hoisting, differences between var, let and const, arrow functions, recursion, arguments.callee, memoization, and promises. It also briefly discusses the history of JavaScript, from its creation in 1995 and renaming to JavaScript in 1996 to the introduction of EcmaScript to standardize the language. The agenda outlines explanations and demonstrations of these JavaScript fundamentals concepts.

Episode 24 - Live Q&A for getting started with SalesforceJitendra Zaa

Episode 19 - Asynchronous Apex - Batch apex & schedulersJitendra Zaa

This document provides an overview of asynchronous processing in Salesforce using Batch Apex and Scheduled Apex. It discusses the differences between synchronous and asynchronous processing, how to structure Batch Apex jobs with start, execute, and finish methods, how to maintain state across batches, considerations for Batch Apex, how Scheduled Apex jobs work based on cron expressions, anatomy of a Scheduled Apex job, and considerations for Scheduled Apex. The document includes demos of writing basic and stateful Batch Apex jobs and a Scheduled Apex job with a cron trigger.

Episode 17 - Handling Events in Lightning Web ComponentJitendra Zaa

This document outlines an agenda for an event on communicating between Lightning Web Components in Salesforce. It will introduce the Salesforce Playground, demonstrate communication between parent and child components and between sibling components, have a Q&A session, and provide references. The speaker is a Salesforce MVP with 23 certifications who will guide attendees through demos and answer questions to help beginners start their Salesforce coding adventure using events in Lightning Web Components.

Episode 16 - Introduction to LWCJitendra Zaa

The document provides an agenda and overview for an introduction to Lightning Web Components (LWC) presentation. It discusses the pillars of modern web development, why LWC was developed, the development tools needed for LWC, the anatomy of an LWC, the LWC lifecycle methods, decorators used in LWC, includes demos of creating an LWC and a Hello World component, compares LWC to Aura components, and lists additional resources. The presentation aims to give attendees an understanding of LWC fundamentals.

Introduction to mulesoft - Alpharetta Developer Group MeetJitendra Zaa

This document provides an introduction and overview of Mulesoft. It discusses Mulesoft's history, from its founding in 2006 to its acquisition by Salesforce in 2018. It also outlines Mulesoft's API-led approach to integration and its deployment models, including runtime manager to cloudhub, cloud console to your own servers in a hybrid model, and on-premises console to on-premises deployment. The agenda includes presentations on Mulesoft history, API-led connectivity, deployment models, demos, and a Q&A session.

Episode 12 - Basics of TriggerJitendra Zaa

This document provides an overview of Apex triggers in Salesforce, including: 1. Apex triggers enable custom actions before or after changes to Salesforce records like inserts, updates, or deletions. Triggers execute based on insert, update, delete, merge, upsert, or undelete operations. 2. Context variables provide information about the trigger context like isExecuting, isInsert, and record collections like new, newMap, old, and oldMap. 3. Before triggers are used to update or validate record values before they are saved, while after triggers can access system-set field values and affect other records through logging or asynchronous events. Records in after triggers are read-only.

Episode 11 building & exposing rest api in salesforce v1.0Jitendra Zaa

Episode 10 - External Services in SalesforceJitendra Zaa

This document provides an overview and agenda for setting up and using external services in Salesforce Flow (Visual Workflow). It begins with introducing external services as a way to consume APIs without code. It then outlines the steps to set up a named credential and register an external service. This is followed by a live demo of how to use external services in a Flow. Resources for learning more about external services on Trailhead are provided at the end.

Episode 14 - Basics of HTML for SalesforceJitendra Zaa

This document provides an agenda and overview for an introduction to HTML coding basics. It includes 3 sentences: The document outlines an agenda to cover introduction to HTML tags, text formatting, headings, paragraphs, comments, images, links, lists, forms, tables, cascading style sheets (CSS), and various CSS properties. It provides examples of common HTML elements and tags as well as how to structure an HTML page and insert different types of content. The session will conclude with allowing time for questions and answers.

South East Dreamin 2019Jitendra Zaa

This document discusses setting up Continuous Integration using SalesforceDX and Jenkins. It covers: 1. The problem of long, complex builds and the need to reduce time from development to production. 2. An overview of Jenkins and why it is used for Continuous Integration, including that it is open source and has over 1000 plugins. 3. The history and evolution of Jenkins from its origins in Hudson to becoming the dominant CI tool today. 4. The concepts of Continuous Integration, Continuous Delivery, and Continuous Deployment and how branching strategies fit in. 5. A demo of setting up Jenkins and SFDX for Continuous Integration, including creating certificates, connected apps, environment variables, and Jenkins projects

Episode 9 - Building soap integrations in salesforceJitendra Zaa

Episode 8 - Path To Code - Integrate Salesforce with external system using R...Jitendra Zaa

Episode 6 - DML, Transaction and Error handling in SalesforceJitendra Zaa

This document provides an agenda and overview for a session on performing data manipulation language (DML) operations and handling errors in Salesforce. It discusses how to insert, update, delete, upsert, undelete, and merge records using DML. It also covers bulk DML, database methods for DML, transaction control using savepoints and rollbacks, and handling errors. The session aims to teach attendees how to manipulate records and handle errors when working with data in Salesforce.

Lightning Web Component in SalesforceJitendra Zaa

1. Lightning Web Components introduce a new programming model built on modern web standards that provides enhanced productivity, performance, and compatibility. 2. They allow more code to be executed by the browser instead of JavaScript abstractions for improved performance. 3. Lightning Web Components can coexist and interoperate with existing Lightning components and can be composed with clicks or code.

Episode 4 - Introduction to SOQL in SalesforceJitendra Zaa

SOQL is used to query records from the Salesforce database. It includes clauses like SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, and LIMIT. The WHERE clause restricts rows returned using conditions, operators like equal, not equal, less than and logical operators. Relationship and aggregate functions can also be used. SOQL in Apex allows querying records in batches of 200 using for loops. SOSL performs full text searches across objects and includes clauses like FIND, IN, and RETURNING.

Episode 2 conditional flows & loopsJitendra Zaa

Build sfdx plugin in 15 minutesJitendra Zaa

The document discusses how to build a Salesforce DX plugin in 15 minutes. It provides an overview of Salesforce DX and the Salesforce CLI. Salesforce DX allows developers to create custom plugins on top of the Salesforce CLI. The presenters demonstrate how to generate a basic Salesforce DX plugin using the plugin generator. It requires knowledge of Node.js, TypeScript, and using Yarn for dependency management. The plugin can then connect to Salesforce orgs and use the REST API. Resources are provided to learn more about Salesforce DX, the CLI, and creating custom plugins.

Salesforce Org lifecycle management : empowering adminsJitendra Zaa

Episode 13 - Advanced Apex TriggersJitendra Zaa

Episode 15 - Basics of JavascriptJitendra Zaa

Episode 24 - Live Q&A for getting started with SalesforceJitendra Zaa

Episode 19 - Asynchronous Apex - Batch apex & schedulersJitendra Zaa

Episode 17 - Handling Events in Lightning Web ComponentJitendra Zaa

Episode 16 - Introduction to LWCJitendra Zaa

Introduction to mulesoft - Alpharetta Developer Group MeetJitendra Zaa

Episode 12 - Basics of TriggerJitendra Zaa

Episode 11 building & exposing rest api in salesforce v1.0Jitendra Zaa

Episode 10 - External Services in SalesforceJitendra Zaa

Episode 14 - Basics of HTML for SalesforceJitendra Zaa

South East Dreamin 2019Jitendra Zaa

Episode 9 - Building soap integrations in salesforceJitendra Zaa

Episode 8 - Path To Code - Integrate Salesforce with external system using R...Jitendra Zaa

Episode 6 - DML, Transaction and Error handling in SalesforceJitendra Zaa

Lightning Web Component in SalesforceJitendra Zaa

Episode 4 - Introduction to SOQL in SalesforceJitendra Zaa

Episode 2 conditional flows & loopsJitendra Zaa

Build sfdx plugin in 15 minutesJitendra Zaa

Salesforce Org lifecycle management : empowering adminsJitendra Zaa

Recently uploaded (20)

YSPH VMOC Special Report - Measles Outbreak Southwest US 4-30-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

A measles outbreak originating in West Texas has been linked to confirmed cases in New Mexico, with additional cases reported in Oklahoma and Kansas. The current case count is 795 from Texas, New Mexico, Oklahoma, and Kansas. 95 individuals have required hospitalization, and 3 deaths, 2 children in Texas and one adult in New Mexico. These fatalities mark the first measles-related deaths in the United States since 2015 and the first pediatric measles death since 2003. The YSPH Virtual Medical Operations Center Briefs (VMOC) were created as a service-learning project by faculty and graduate students at the Yale School of Public Health in response to the 2010 Haiti Earthquake. Each year, the VMOC Briefs are produced by students enrolled in Environmental Health Science Course 581 - Public Health Emergencies: Disaster Planning and Response. These briefs compile diverse information sources – including status reports, maps, news articles, and web content– into a single, easily digestible document that can be widely shared and used interactively. Key features of this report include: - Comprehensive Overview: Provides situation updates, maps, relevant news, and web resources. - Accessibility: Designed for easy reading, wide distribution, and interactive use. - Collaboration: The “unlocked" format enables other responders to share, copy, and adapt seamlessly. The students learn by doing, quickly discovering how and where to find critical information and presenting it in an easily understood manner.

Stein, Hunt, Green letter to Congress April 2025Mebane Rash

GDGLSPGCOER - Git and GitHub Workshop.pptxazeenhodekar

Handling Multiple Choice Responses: Fortune Effiong.pptxAuthorAIDNationalRes

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

Political History of Pala dynasty Pala Rulers NEP.pptxArya Mahila P. G. College, Banaras Hindu University, Varanasi, India.

The Pala kings were people-protectors. In fact, Gopal was elected to the throne only to end Matsya Nyaya. Bhagalpur Abhiledh states that Dharmapala imposed only fair taxes on the people. Rampala abolished the unjust taxes imposed by Bhima. The Pala rulers were lovers of learning. Vikramshila University was established by Dharmapala. He opened 50 other learning centers. A famous Buddhist scholar named Haribhadra was to be present in his court. Devpala appointed another Buddhist scholar named Veerdeva as the vice president of Nalanda Vihar. Among other scholars of this period, Sandhyakar Nandi, Chakrapani Dutta and Vajradatta are especially famous. Sandhyakar Nandi wrote the famous poem of this period 'Ramcharit'.

SCI BIZ TECH QUIZ (OPEN) PRELIMS XTASY 2025.pptxRonisha Das

How to track Cost and Revenue using Analytic Accounts in odoo Accounting, App...Celine George

Analytic accounts are used to track and manage financial transactions related to specific projects, departments, or business units. They provide detailed insights into costs and revenues at a granular level, independent of the main accounting system. This helps to better understand profitability, performance, and resource allocation, making it easier to make informed financial decisions and strategic planning.

To study Digestive system of insect.pptxArshad Shaikh

Presentation on Tourism Product Development By Md Shaifullar RabbiMd Shaifullar Rabbi

K12 Tableau Tuesday - Algebra Equity and Access in Atlanta Public Schoolsdogden2

Algebra 1 is often described as a “gateway” class, a pivotal moment that can shape the rest of a student’s K–12 education. Early access is key: successfully completing Algebra 1 in middle school allows students to complete advanced math and science coursework in high school, which research shows lead to higher wages and lower rates of unemployment in adulthood. Learn how The Atlanta Public Schools is using their data to create a more equitable enrollment in middle school Algebra classes.

pulse ppt.pptx Types of pulse , characteristics of pulse , Alteration of pulsesushreesangita003

YSPH VMOC Special Report - Measles Outbreak Southwest US 5-3-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

A measles outbreak originating in West Texas has been linked to confirmed cases in New Mexico, with additional cases reported in Oklahoma and Kansas. The current case count is 817 from Texas, New Mexico, Oklahoma, and Kansas. 97 individuals have required hospitalization, and 3 deaths, 2 children in Texas and one adult in New Mexico. These fatalities mark the first measles-related deaths in the United States since 2015 and the first pediatric measles death since 2003. The YSPH Virtual Medical Operations Center Briefs (VMOC) were created as a service-learning project by faculty and graduate students at the Yale School of Public Health in response to the 2010 Haiti Earthquake. Each year, the VMOC Briefs are produced by students enrolled in Environmental Health Science Course 581 - Public Health Emergencies: Disaster Planning and Response. These briefs compile diverse information sources – including status reports, maps, news articles, and web content– into a single, easily digestible document that can be widely shared and used interactively. Key features of this report include: - Comprehensive Overview: Provides situation updates, maps, relevant news, and web resources. - Accessibility: Designed for easy reading, wide distribution, and interactive use. - Collaboration: The “unlocked" format enables other responders to share, copy, and adapt seamlessly. The students learn by doing, quickly discovering how and where to find critical information and presenting it in an easily understood manner. CURRENT CASE COUNT: 817 (As of 05/3/2025) • Texas: 688 (+20)(62% of these cases are in Gaines County). • New Mexico: 67 (+1 )(92.4% of the cases are from Eddy County) • Oklahoma: 16 (+1) • Kansas: 46 (32% of the cases are from Gray County) HOSPITALIZATIONS: 97 (+2) • Texas: 89 (+2) - This is 13.02% of all TX cases. • New Mexico: 7 - This is 10.6% of all NM cases. • Kansas: 1 - This is 2.7% of all KS cases. DEATHS: 3 • Texas: 2 – This is 0.31% of all cases • New Mexico: 1 – This is 1.54% of all cases US NATIONAL CASE COUNT: 967 (Confirmed and suspected): INTERNATIONAL SPREAD (As of 4/2/2025) • Mexico – 865 (+58) ‒Chihuahua, Mexico: 844 (+58) cases, 3 hospitalizations, 1 fatality • Canada: 1531 (+270) (This reflects Ontario's Outbreak, which began 11/24) ‒Ontario, Canada – 1243 (+223) cases, 84 hospitalizations. • Europe: 6,814

Social Problem-Unemployment .pptx notes for Physiotherapy StudentsDrNidhiAgarwal

Unemployment is a major social problem, by which not only rural population have suffered but also urban population are suffered while they are literate having good qualification.The evil consequences like poverty, frustration, revolution result in crimes and social disorganization. Therefore, it is necessary that all efforts be made to have maximum. employment facilities. The Government of India has already announced that the question of payment of unemployment allowance cannot be considered in India

Exploring-Substances-Acidic-Basic-and-Neutral.pdfSandeep Swamy

Exploring Substances: Acidic, Basic, and Neutral Welcome to the fascinating world of acids and bases! Join siblings Ashwin and Keerthi as they explore the colorful world of substances at their school's National Science Day fair. Their adventure begins with a mysterious white paper that reveals hidden messages when sprayed with a special liquid. In this presentation, we'll discover how different substances can be classified as acidic, basic, or neutral. We'll explore natural indicators like litmus, red rose extract, and turmeric that help us identify these substances through color changes. We'll also learn about neutralization reactions and their applications in our daily lives. by sandeep swamy

SPRING FESTIVITIES - UK AND USA -Colégio Santa Teresinha

How to Set warnings for invoicing specific customers in odooCeline George

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

The ever evoilving world of science /7th class science curiosity /samyans aca...Sandeep Swamy

The Ever-Evolving World of Science Welcome to Grade 7 Science4not just a textbook with facts, but an invitation to question, experiment, and explore the beautiful world we live in. From tiny cells inside a leaf to the movement of celestial bodies, from household materials to underground water flows, this journey will challenge your thinking and expand your knowledge. Notice something special about this book? The page numbers follow the playful flight of a butterfly and a soaring paper plane! Just as these objects take flight, learning soars when curiosity leads the way. Simple observations, like paper planes, have inspired scientific explorations throughout history.

Operations Management (Dr. Abdulfatah Salem).pdfArab Academy for Science, Technology and Maritime Transport

YSPH VMOC Special Report - Measles Outbreak Southwest US 4-30-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

Stein, Hunt, Green letter to Congress April 2025Mebane Rash

GDGLSPGCOER - Git and GitHub Workshop.pptxazeenhodekar

Handling Multiple Choice Responses: Fortune Effiong.pptxAuthorAIDNationalRes

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

Political History of Pala dynasty Pala Rulers NEP.pptxArya Mahila P. G. College, Banaras Hindu University, Varanasi, India.

SCI BIZ TECH QUIZ (OPEN) PRELIMS XTASY 2025.pptxRonisha Das

How to track Cost and Revenue using Analytic Accounts in odoo Accounting, App...Celine George

To study Digestive system of insect.pptxArshad Shaikh

Presentation on Tourism Product Development By Md Shaifullar RabbiMd Shaifullar Rabbi

K12 Tableau Tuesday - Algebra Equity and Access in Atlanta Public Schoolsdogden2

pulse ppt.pptx Types of pulse , characteristics of pulse , Alteration of pulsesushreesangita003

YSPH VMOC Special Report - Measles Outbreak Southwest US 5-3-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

Social Problem-Unemployment .pptx notes for Physiotherapy StudentsDrNidhiAgarwal

Exploring-Substances-Acidic-Basic-and-Neutral.pdfSandeep Swamy

SPRING FESTIVITIES - UK AND USA -Colégio Santa Teresinha

How to Set warnings for invoicing specific customers in odooCeline George

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

The ever evoilving world of science /7th class science curiosity /samyans aca...Sandeep Swamy

Operations Management (Dr. Abdulfatah Salem).pdfArab Academy for Science, Technology and Maritime Transport

Episode 21 - Design Pattern 1

1. Path to Code Begin Your Salesforce Coding Adventure

2. Episode 21 Design Pattern - Part 1

3. Jitendra Zaa Salesforce MVP Sr Technical Architect 23x Certified @Jitendra Zaa Speaker

4. Agenda • SOLID • Design Principles • What are design Patterns • Who are Gang Of Four • GoF Patterns • Creational Pattern • Example

5. Some House Rules • Please mute your mic • Keep adding questions in Zoom Q&A Window • No question is too small • Questions will be answered in last 15 mins

6. SOLID Design Principles

7. Open Closed Principle Class should be Open for extension but Closed for Modification.

8. Example Create a Program to accept Circle and Square Object and return Sum of their Area.

9. Example

12. Run Code

13. Change in Requirement Add Support for Rectangle Also. What would you do ? Add one more If else? That would be breaking Open Closed Principle. Class should be closed to modification but open to Extension.

14. Solution Add Interface so that all Shape should follow that interface, new Class will become

15. Single Responsibility Principle A class should have one and only one reason to change that means only one job.

16. Example

19. Question AreaCalculator class calculates area and returns result of sum of area of all Shapes. How to add functionality if we want to get area result as JSON or HTML ?

20. Answer Incorrect

21. Explanation Its breaking Single Responsibility Principle. AreaCalculator should only change if formula related to Area changes

22. Liskov Substitution Principle If class B is a child of class A, then A can be replaced by B, without changing anything in a program. In other words, the LSP principle states that you should not encounter unexpected results if child (derived) classes are used instead of parent classes.

23. Interface Segregation Principle This states that do not force a child class to depend on a method that is not used for them. This principle suggests that you break interfaces into smaller ones so that a client can only implement an interface that is of interest.

24. Interface Segregation Principle

25. Dependency Inversion Principle This states that modules should not depend on each other directly and should depend via an interface (abstraction).

26. What are Design Patterns ? Each Pattern describes 1. A problem which occurs again and again 2. A core of the Solution 3. Consequences of Solution

27. Design Patterns Does not Provide Actual Implementation Details

28. Example - Roof Patterns in Construction

29. Who are Gang of Fours Book written in 1994 consist of 23 Design patterns by 1. Erich Gamma 2. Richard Helm 3. Ralph Johnson 4. John Vlissides

30. Gang of Four Patterns Creational Patterns Structural Behavioral 1. Abstract Factory 6. Adapter 13. Chain of responsibility 2. Builder 7. Bridge 14. Command 3. Factory Method 8. Composite 15. Intercepter 4. Prototype 9. Decorator 16. Iterator 5. Singleton 10. Facade 17. Mediator 11. Fly Weight 18. Memento 12. Proxy 19. Observer 20. State 21. Strategy 22. Template Method 23. Visitor

31. Reference • Apex Design Patterns • SOLID Principle

32. Q&A

33. Next Episode 22 Design Pattern - 2

34. Thanks

Episode 21 - Design Pattern 1

Recommended

More Related Content

What's hot (20)

Similar to Episode 21 - Design Pattern 1 (20)

More from Jitendra Zaa (20)

Recently uploaded (20)

Episode 21 - Design Pattern 1