Let's start out with something fun - Your own game!!
- Individual project
- Be creative, make it fun and interesting
- Work through tough programming challenges
Show us what you've got!
- Render a game in the browser with JavaScript
- Switch turns between two players
- Design logic for winning & visually display which player won
- GIT for version control
- HTML5 with Semantic Markup
- CSS3 styling
- JavaScript
- YAGNI (You aren't gonna need it)
- KISS (Keep It Simple Stupid)
- DRY (Don't Repeat Yourself)
- SOLID (Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion)
- Organize your
HTML/CSS/JavaScript/Assetsfiles into folders- Assets should separate: images, fonts, libraries, etc
- Validated HTML with the W3C HTML Validation tool
- JavaScript code is linted with JSLint
- Deploy your game online, where the rest of the world can access it
- Your game must be hosted publicly
- Your repo must be hosted in the WDI-HK-8 organization
- Don't forget to add a link to your hosted working game in the URL section of your repo
- Git Commits
- Explanatory Commit messages
- We expect frequent commits dating back to the very beginning of the project
- Use branches and pull requests
- Only include in PR related files to the functionality you want to add
- Clear and comprehensive PR comments
- Leverage Github-flavored Markdown
- Project must have a
readme.mdcontaining:- Introduction to the game
- Game rules
- Technologies used
- Design approach
- Installation instructions (
git clone,bower, ) - Unsolved problems / Upcoming features
- Author contact information
- Break the project down into different components (data, presentation, views, style, DOM manipulation) and brainstorm each component individually. Use whiteboards!
- Use Chrome's Development Tools (console.log, inspector, alert statements, etc) to debug and solve problems
- Work through the lessons in class & ask questions when you need to! Think about adding relevant code to your game each night, instead of, you know... procrastinating.
- Commit early, commit often. Don’t be afraid to break something because you can always go back in time to a previous version.
- Consult documentation resources (MDN, jQuery, etc.) at home to better understand what you’ll be getting into.
- Don’t be afraid to write code that you know you will have to remove later. Create temporary elements (buttons, links, etc) that trigger events if real data is not available. For example, if you’re trying to figure out how to change some text when the game is over but you haven’t solved the win/lose game logic, you can create a button to simulate that until then.
Make a one player game where people down on their luck can lose all their money by guessing which card the computer will deal next!
Sometimes just called "Memory", it's a card game in which all of the cards are laid face down on a surface and two cards are flipped face up over each turn. If you get all the matching cards, you've won!
Test your wits & knowledge with whatever-the-heck you know about (so you can actually win). Guess answers, have the computer tell you how right you are!
- MDN Javascript Docs (a great reference for all things Vanilla Javascript)
- jQuery Docs (if you're using jQuery)
- Github Pages (for hosting your game)
- Did you complete the user stories, wireframes, task tracking, and/or ERDs, as specified above?
- Did you use source control as expected for the phase of the program you’re in (detailed above)?
- Did you deliver a project that met all the technical requirements?
- Given what the class has covered so far, did you build something that was reasonably complex?
- Did you added a personal spin or creative element into your project submission?
- Did you deliver something of value to the end user (not just a login button and an index page)?
- Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming?
- Did you comment your code as your instructors have in class?
- Did you remove commented code?
- Are you able to defend why you implemented your solution in a certain way?
- Can you demonstrate that you thought through alternative implementations?
- (Note that this part of your feedback evaluation will take place during your one-on-one code review with your instructors, after you've completed the project.)
Your instructors will give you a total score on your project between:
| Score | Expectations |
|---|---|
| 0 | Does not meet expectations. |
| 1 | Meets expectactions, good job! |
| 2 | Exceeds expectations, you wonderful creature, you! |
This will serve as a helpful overall gauge of whether you met the project goals, but the more important scores are the individual ones above, which can help you identify where to focus your efforts for the next project!
