Devlogs and hours

Software hours come from Hackatime, unfortantely we run into situations where we can't use hackatime. That's what devlogs are for. You only get rewarded hours for the hours we see you work. That's why we created lapse. Use lapse to log your hours, and enter the url into the devlogs on the site. You may need to create a project first before creating devlogs.

How hours are counted#

Hackatime watches your editor and reports which project you're working on. It only tracks hour you've worked since setting it up, which is why getting set up first matters so much.

What counts:

• Time in your editor on the project you submit.
• Time spent on the parts that aren't code, when you're editing files configs, compose files, documentation.

What doesn't:

• Time before the plugin was installed.
• Time on a different project, even a related one.
• Reading, planning, and thinking away from the keyboard. Real work, uncounted work.

Devlogs#

A devlog is a short post about what you just did. Write one when you finish something tracked by lapse, not on a schedule:

• What you built. One or two sentences.
• A link. A link to a video of you working.

Good devlogs are short, specific and frequent. "Got the transcoder working turns out the container needed /dev/dri passed through for hardware decoding" is worth ten times "worked on video stuff today".

They also make reviews easier and faster, when you've written eight devlogs, your project description writes itself.

If you ever need any help with devlogs you should check the slack channel