pt-course-18-19

Week 4: Configs & Requirements

Table of Contents

• Comic
• Slides
• Assignments
• Homework

Comic

GeoIP by @xkcd.

Slides

• Slides

Assignments

Linting (research)

• Research
• Time: 0:45h
• Goals: subgoal 5

Take about 0:45h to investigate what ‘linting’ is: what is it used for, why is it useful and try to look for examples.

• Linting is commonly used to enforce consistent ‘code quality’, what do we mean by that?
• What are common tools for ‘linting’?
• How can you implement these tools in your own project?
• What are the difference between syntax and stylistic errors?

Homework

Linting (implementation)

• Homework
• Time: 3h
• Goals: subgoal 5

Based on the research you conducted setup a (or multiple) linters in your own project. Ask yourself which tools are useful for your own project. If you’re not sure which one to pick, the ones below are solid choices:

• eslint - pluggable linting utility for JavaScript
• stylelint - modern linter that helps you avoid errors and enforce conventions in your styles
• prettier - opinionated code formatter
• And so much more

Think about what rules you are going to enforce. Most linters requires you to configure those on your own. You can use linters most linters as script in your package.json or as an extension in your editor.

If you’ve configured a linter and want to use it in your editor, make sure you also install the corresponding extension!

Extensions

• Homework
• Time: 2h
• Goals: subgoal 5

Previously you’ve customized the look and feel of your command line. We are going to do the same thing with your code editor. Since you spend quite some time in there it’s good to customize it to your own liking. If you are still using Brackets, this might be a good assignment to broaden your horizon or even switch to another code editor such as Atom or VS Code.

• Try a different color theme! Each editor come with some default options but you can also browse through lots of other community made ones.
  • In VS Code these are called color themes.
  • Here is a list for Atom, they are usually split between UI and syntax themes.
• Install some extensions to enhance functionality of your editor.
  • VS Code marketplace and Atom Packages are the corresponding pages for extensions for both editors.
• Get the most out of your edidtor by tweaking your settings and getting to know the shorcuts. Take some time to tweak some settings and learn some keyboard shortcuts. You can read the Flight Manual for Atom or read the docs for VS Code

Wes and Scott (you might have taken one of their courses) have a good podcast called Syntax where they detail their setups. You can listen to these episodes or look in the show notes for inspiration.

Usability Test

• Homework
• Time: 1h
• Goals: subgoal 5

You already started working on your interface. You might already have some sketches or written some views, partials or components with a templating engine. Collect feedback on your interface and Static HTML. Let other students test your interface and give you feedback.

Methods

• Usability Test

Requirements List

• Homework
• Time: 1h
• Goals: subgoal 5

Narrow down your Job Story in specific small functionalities and make a list of requirements your feature should have. You can then apply the MoSCoW method on your list to see which functionalities are must-haves and which ones are enhancements.

Methods

• Requirements List
• MoSCoW method

Hand in

1. Pages: Create a page for this week or section of your research on your GitHub Wiki.

2. Push your changes: Hand in your research in your repository on GitHub under your username.

This site is open source. Improve this page.