-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtext.txt
97 lines (64 loc) · 3.57 KB
/
text.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
=============Project Requirements
1. Built with HTML, CSS and JavaScript (must be visual and use the DOM not the Console)
2. Hosted on Github pages
3. Commits to Github every day
4. A README.md file with explanations of the technologies used, the approach taken, a link to your live site, installation instructions, unsolved problems, etc
OPTION 1:You build a story:
1. Must have two Classes and one instance of each class
- Example: make a Dog Class and create a Dog named Sam
- Example: make a Person Class and create a Person named John
2. Story must be controlled by buttons
3. Must use Flexbox
4. Must have a reset button
Option 2: You build a game
1. Must be a two player game (either against the computer or against another player)
- Example: Blackjack: A player plays against the dealer. The dealer is the computer
- Example: Connect Four: Two players pass the game between themselves to take turns
2. A win state - a way for the player to win the game
- High score can be considered a win state
3. A lose state - a way for the player to lose the game
- Example: Blackjack - a player must be able to lose all of their money with losing hands and cannot play if their bankroll is at 0
- Example: Connect Four - the other player has won or there are no possible plays left
4. A way to keep playing if the game is not over
5. Multiple rounds to play:
- a round must begin,
- end,
- and there must be a way to check if the game should continue or the overall game is won or lost
- Example: Blackjack: a player takes turns playing a hand versus a computer - the player's hand can either win, lose or tie the dealer.
- If the player has enough money in their bankroll they can keep playing.
- A player must be able to win several rounds and increase their bankroll
- Example: Connect Four: two (non-computer) players take turns adding chips to the board.
- The game will check if a player won or if the board is full and there are no more plays possible.
- A player gets four chips in a row (vertically or horizontally)
- one person wins, one loses, there are no further plays in this case
Stretch Goals (Not Mandatory):
Recommended Features
- A way to reset the board and play again
- CSS to give your game a personal and fun style
- Responsive mobile design
- Work with your instructor to determine additional stretch goals
- GitHub Pages:
https://staceyjo.github.io/Snake/
Technical Demonstration:
- Be approximately 5 minutes in length
Remember:
If you didn’t complete your game. It’s okay! BREATHE! It is common for many to not finish.
Practice selling yourself, love your craft, and pretend you’re presenting to your future employer.
Do not sell yourself short. Only show things that are working or present positively if nothing is working.
Save all the technical challenges towards the end.
Have your code ready on your screen, and your game running on the browser.
Be prepared!
Respect, boundaries, rules, and expectations still apply.
Show off all features of the app
Show us your game in the browser
Play a couple of rounds
Explain the technical details
Show your code - we don’t have a lot of time to show everything, but show which ones you were proud of, new things you learned, and/or successes
Explain the technical challenges
This is the only time you will talk about blockers, and challenges
Try not to say negative comments about yourself, and just focus on the challenges
Explain which improvements you might make
Blockers and challenges goals
Time management improvements
First project thoughts, and challenges
Be prepared to answer questions from the instructors and other students.