Home

Welcome to the RealSkill support wiki!

#How to write a good task

A good task has good tests

Tests are a must, because it's the only way our Jenkins can check solution correctness. Test scenarios should help developer to properly adjust their solution.

Minimize dependencies

If developer's task is to write DAO layer then probably there is no need to create project with REST layer.

Use fixed versions in bower.json and package.json

By default bower and package add dependencies like this:

q:"^0.1.0"

Note the ^. If new version arrives (i.e. 0.1.1) then developer will have that version installed, but what if that version introduces a bug? It's not a rare case, so better define your dependencies without ~ and ^:

q:"0.1.0"

Make sure package names in bower.json and package.json are meaningful

Do not use dots, exclamation or question marks in task title

Should tasks have Documentation or Before you start sections?

RealSkill can be used to examine skill of developer and also as a help during training. Examine tasks' readmes should not contain links to documentations, hint videos, etc. On the other hand, we encourage training exercises to include links to documentations, videos and other helpful learning materials.