Skip to content

uziwhoavg/Module_3_UZINCU608_PTO2403_Group-C_UZI-NCUBE_JSL03

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 

Repository files navigation

[JSL03] Project Submission: Which one is which? Declarative or Imperative?!

Loom Recording Link: EXAMPLE1 EXAMPLE12

Presentation Talking Points

Example #: [Insert Example Number]

Imperative Approach [2 Minutes]

  1. Step-by-Step Explanation: Start by explaining the code logic in the imperative approach.

    • Mention each step of the process in the code.
    • Describe how the code provides explicit instructions for each action.
    • Discuss the use of variables to track the state and progress of the process.
  2. Emphasis on How: Highlight how the imperative approach focuses on detailing "how" the task is accomplished.

    • Point out the use of loops, conditions, and explicit instructions.
    • Discuss any mutable variables or states that change during execution.

Example #: [Insert Example Number]

Declarative Approach [2 Minutes]

  1. High-Level Process Description: Explain the code logic in the declarative approach.

    • Describe the cooking process in a high-level, abstract manner.
    • Emphasize that the code defines "what" should happen rather than "how" it should happen.
  2. Use of Data Structures: Discuss the use of data structures (e.g., arrays, objects) to represent the process steps.

    • Explain how the process steps are organized in a structured format.
    • Mention any abstraction layers or functions used to encapsulate actions.

Learning Outcome [1 Minute]

  • Reflect on what you've learned from analyzing these code examples in different paradigms.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 100.0%