Skip to content

Latest commit

 

History

History
76 lines (52 loc) · 3.01 KB

week-4.md

File metadata and controls

76 lines (52 loc) · 3.01 KB
Raw

Week 4:Production Setup

No Deploy Fridays

— @iamdevloper

Table of Contents

Slides

Assignments

Refactor

Refactor Banner

Ensure your code (and repo in general) is neat-o

Synopsis

  • Time: 3h-4h (depending on your work so far)
  • Due: before week 5

Anyone can write code that a computer can understand. Good programmers write code that humans can understand.

Martin Fowler

The code you write will be executed by computers, but it will exclusively be read by humans. Therefore, it's critical that your code is easy to read, understand, and "mentally parse". Go back into your work so far and make sure that everything you've done so far is easy to understand for "outsiders" to your project.

Assignment

  • Pick (minimum) 5 of the Clean Code JavaScript concepts from the GitHub repo and refactor parts of your client and or server-side JavaScript code. Additionally clean-up any other code that needs refactoring. Document what you refactored with before and after code blocks in your wiki.
  • Tweak or set-up additional linters (see week-3) in your project. It will further help you spot any inconsistenties in your code.
  • Ask your support group to review your work, and optimize your code based on the questions they ask. It can be surprisingly difficult to find problems in work you're too familiar with.
  • Make sure that files like your .env file (with your private information), node_modules and other files that are not part of your project, are listed in .gitignore and are not present in your repo.
Further Reading

Concept

Continue working on your Job Story and feature you are going to build for Blok Tech.
Improve the front-end interface of your feature, improve the quality of the code, write documentation etc.

Hand In

  1. Push your Changes
    Commit and push any progress in your repo. Document all research you did in your wiki.

  2. Create an Issue
    Mark this assignment as complete by opening an issue on our GitHub issue tracker. Fill in the progress report template with your own information. Include what progress you made in the description of the issue.

  3. Feedback
    Any thoughts/feelings/concerns/opinions about these assignments? Let us know! We optimize these classes year-to-year, so your feedback is invaluable in making this course better.