Zeynep: Welcome to JS, 3 weeks

[Melati5]

Learning Objectives

all of these skills are limited to short, single-page programs written with Just Enough JavaScript

Priorities: 🥚, 🐣, 🐥, 🐔 (click to learn more)

There is a lot to learn in this repository. If you can't master all the material at once, that's expected! Anything you don't master now will always be waiting for you to review when you need it. These 4 emoji's will help you prioritize your study time and to measure your progress: - 🥚: Understanding this material is required, it covers the base skills you'll need for this module and the next. You do not need to finish all of them but should feel comfortable that you could do them with enough time. - 🐣: You have started all of these exercises and feel you could complete them all if you just had more time. It may not be easy for you but with effort you can make it through. - 🐥: You have studied the examples and started some exercises if you had time. You should have a big-picture understanding of these concepts/skills, but may not be confident completing the exercises. - 🐔: These concepts or skills are not necessary but are related to this module. If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push yourself without getting distracted from the module's main objectives. ---

1. What is Programming

What is a program? What is a programming language? How do programs and people fit together?

• [x] 🥚 Data in, Data Out: You understand that computer programs are used to transform data, and can explain a JS program from this module in terms of the data that goes in and the data that comes out.
• 🥚 Three Audiences: You can explain how a single file of code is used to communicate with 3 different audiences:
  • [x] Developers: You can explain how code formatting, comments, logs and variable names make it easier (or harder!) for a developer to understand a program.
  • [x] Computers: You can explain how a computer follows your instructions to store, read and modify data in program memory.
  • [x] Users: You can explain how the computer creates a dynamic user experience by following different executions paths depending on user input.
• [ ] 🥚 Tracing Variables: You can complete a trace table for a program that uses only variables, and can check your work using the "trace" button.
• 🥚 JavaScript Syntax: Given a program, you can identify these parts of JavaScript syntax:
  • [x] Primitives
  • [x] Operators
  • [x] Identifiers
  • [x] Keywords
  • [ ] Checks
  • [ ] Blocks
  • [ ] Function Calls
• [x] 🥚 Pseudo Code: You can explain what pseudo code is, how it's used and why it's helpful.
• [x] 🥚 Program Goals: You understand that a full JavaScript program can be explained as a series of smaller goals, and can write names for the goals in a simple working program.
• 🐣 Program Analysis: You can study a simple working program and identify:
  • [x] The program's behavior (data in, data out)
  • [x] The program's goals
  • [x] The program's syntax and language features
  • [x] Which parts of the source code are for which audience (users, devs, computers)
• [ ] 🐥 Same Behavior, Different Code: You can study simple programs with the same behavior (data in, data out) but different source code and explain how the differences matter for each audience.

2. Just Enough JavaScript

Go in depth on JavaScript you need to know for writing interactive text-based programs in the browser. Along the way you will learn how each language feature works in small programs.

• 🥚 Listening and Reading: You can read code out loud, and understand your classmates when they read code to you. You don't need to understand how a program works to master these learning objectives!
  • [x] Listening You can exactly re-write a program that a classmate has read
  • [x] Reading You can read a program out loud and guide your classmates to re-write exactly the same code without them seeing the program. Every indentation, semi-colon, comment and spelling in their program must be identical to yours.
• 🥚 Static vs. Dynamic Analysis: You can explain and use these two ways of studying a program, each can help you understand different aspects of your code. To help understand this concept, the options panel in Study Lenses is organized into static and dynamic study options:
  • [x] Static: Studying the text in a code file without running it. Some static study methods are creating a flowchart, analyzing variables, filling out a trace table, and drawing on code.
  • [x] Dynamic: Running code and studying the computer's behavior. Some dynamic study methods are running code and reading console logs, using the trace button, and stepping through in the debugger or JS Tutor.
• [x] 🥚 Tracing Execution: You can complete a "steps" trace table for all JS language features in Just Enough JavaScript, and can correct your table using console output from the "trace" button.
• [x] 🥚 Analyzing Variables: You can list all the variables in a program, and answer these 5 questions for each variable:
  • Where is the variable declared?
  • What is the variable's scope?
  • Is the variable initialized with a value?
  • How many times is its value used (read) in the program?
  • How many times is the variable assigned a new value?
  • What types are assigned to this variable during the program's execution?
• [x] 🥚 Completing Programs: You can successfully fill in blanks for a program when the missing words are provided, including distractors.
• [x] 🐣 Translating Pseudo Code: Given a program written in Pseudo Code, you can translate it to working JavaScript.
• [x] 🐣 Comparing Programs: You can compare two programs with similar code and explain if they have the same behavior or not. If they do not, you can explain how they behave differently and why.
• [ ] 🐥 Constructing Programs: You can reconstruct a program's lines and indentation, successfully ignoring distractor lines.
• [x] 🐥 Linting: You can find and fix simple linting errors in JavaScript programs.
• [x] 🐔 Writing Programs: You can write small programs that log specific values, or pass specific test cases.

3. Understanding Programs

Learn how to understand a larger programs by finding connections between the details and the big picture. By the end of this chapter you will know how to read a new program and do a simple code review.

• [ ] 🥚 Stepping Through: You can pause a script in a your browser's debugger, arrange the debugger, collapse extra panels, and step through a script written with Just Enough JS. At each point in execution you can make a prediction of the next line before executing, and can check your prediction using the scopes panel.
• [ ] 🥚 Imperative Programming: You can explain what the Imperative Programming paradigm is, and can explain how you know the programs in Welcome to JS are Imperative.
• [ ] 🥚 Logging: You can tracing specific aspects of a program's execution and log them to the console.
• [ ] 🐣 Naming Variables: You can analyze how a variable is used in a program and give it two names:
  • Generic: You can give a generic name to a variable based on how it is used in the program.
  • Specific: You can give a specific name to a variable based on how it's used and the program's domain (the program's specific data and use-case).
• [ ] 🐣 Describing Programs: You can read a program and describe it with comments using to the methodology from /describing-programs:
  1. Zoom Out
  2. Zoom In
  3. Find Connections
  4. Describe Goals
• [x] 🐥 Code Review: Given a working program you can review the code for clarity, correctness and style.

4. Developing Programs

Learn to modify and write larger programs in JavaScript. You'll cover many of the hidden skills necessary to develop quality software and to work collaboratively on a code base.

• [x] 🥚 Program Life Cycle: You can explain the two phases of a program's life cycle.
  1. Creation Phase
  2. Execution Phase
• [x] 🥚 Fixing Errors: You can use the structured comment to describe an error in your program, and can make several educated guesses at how to fix the error.
• [x] 🐣 Fixing Bugs: You can use the structured comment to describe and fix a bug in small programs.
• [x] 🐣 Modifying Programs: You can make small changes in a program to change its behavior without breaking it.
• [x] 🐥 Refactoring: Given a working program, you can make changes to the code without changing the program's behavior.
• [ ] 🐥 Writing Programs: Given a description of a program's behavior (user story + test cases), you can plan goals for the program and write code to pass the tests.
• 🐔 Reverse Engineering: Given a working program with unreadable code, you can:
  • [ ] Give the program a name.
  • [ ] Describe the program's behavior with a user story, acceptance criteria and test cases.
  • [ ] Plan goals for the program.
  • [x] Develop your own working program with the exact same behvior.
• 🐔 Imagining Programs: Given an empty page, you can imagine and develop your own programs using Just Enough JavaScript. This includes:
  • [x] A title.
  • [ ] A description with a user story, acceptance criteria and test cases.
  • [x] Commented goals.
  • [x] Fully working Code.

---

[danielhalasz]

@Melati5 can you please add your check-in comments for the week and after submitting, add the week-1 label?

[Melati5]

Week 1

I Need Help With:

Everytime i tried to workout the exercises i had to start from beginging i didnt understand why

What went well?

i read all and feel excited even though its looks complex a bit to me :) i found nice document about java script and keep reading all ...

What went less well?

sorry for delate cuz i had french exam, i felt sorry that i couldnt give all my time to the course at once, but im trying to do my best. i cant wait to focus more on the course from next month.

Lessons Learned

i have to do nice plan even though i have many other things to do. i have to act every week with a proper plan

Sunday Prep Work

trying to understand deeply till sunday class

[danielhalasz]

Everytime i tried to workout the exercises i had to start from beginging i didnt understand why

can you maybe attach a screenshot? what did you have to start from the beginning?

i found nice document about java script and keep reading all

which document?

i cant wait to focus more on the course from next month.

yeee

[Melati5]

https://static.ohu.edu.tr/uniweb/media/portallar/bilgiislemdairebaskanligi/sayfalar/4607/gubra5r3.pdf its the document what i mentioned its in my language :)

i mean for try to do exercises i have to do everytime npm install -g study-lenses from terminal is that normal for all or its my ignorance im confused xD

[danielhalasz]

i have to do everytime npm install -g study-lenses

wow, why would you have to do that? you just go to the cloned repo and type study

[Melati5]

actually i did but everytime when i turned off my computer its disaapears. but i will do again

[colevandersWands]

so after you restart your computer, when you enter $ study in your terminal it has an error?

[Melati5]

It doesn't give an error but every time I close it, the pages disappear and I can't find another solution until I download it again.

[colevandersWands]

try this, if that doesn't work we'll need to do some more trouble shooting:

• open /welcome-to-js in your terminal
• type study and hit enter

if everything is working, study lenses should open in the browser whatever folder is open in your terminal

[danielhalasz]

and if you want, you can save your solution to each exercise..by hitting the save button

[danielhalasz]

[Melati5]

Okey thank you for your help guys i will save ☺️

[Melati5]

Week 2

I Need Help With:

when i try to do exercise it is more helpful someone checking what i am doing because sometimes im losting

What went well?

i read almost every documents at github ...

What went less well?

i read most but i tried less because im scaring to do mistakes

Lessons Learned

i learned how all systems how works its not so far from html and css its just more details version of all cuz sometimes html and css not including some things but js includes many of new things

Sunday Prep Work

i will do more practices friday and saturday to more understand deeply

[colevandersWands]

Getting lost is normal, and mistakes won't hurt anyone! Your coaches and classmates are around to help you when you need it.

The more you try and the more you ask the faster you will learn. looking forward to your questions in Discord ;)

[Melati5]

thank you Evan I will :)

[danielhalasz]

when i try to do exercise it is more helpful someone checking what i am doing because sometimes im losting

you can also try to organize study groups, to do some exercises together, some classmates are doing that

i read most but i tried less because im scaring to do mistakes

making mistakes is the best way to learn, figuring out the solutions

[Melati5]

Okey l will ask them to make practice together thank you Daniel:)

[Melati5]

Week 3

I Need Help With:

Some codes looks a little bit scaring but if i look carefully im seeing my faults

What went well?

i was thought last week i read a lot but no.There are many of documents to look mostly feeling time not enough to learn and finish to read all documents. And after sunday class i felt a little bit confidence and kept study all week, tried to figured out how codes work I try to do many exemples and im still contiuning

What went less well?

i read most but i tried less because im scaring to do mistakes

Lessons Learned

When you find something more interesting it easy to collect your attention

Sunday Prep Work

i have to study more and more to try other codes until sunday

[danielhalasz]

im seeing my faults

there are no faults, just steps in the learning path

i read most but i tried less because im scaring to do mistakes

mistakes are a great way to learn, do not be scared of them. it is a natural part of learning something new.