Pro tip: If you are a programmer who needs to write a self-eval at the end of the try this:
1) Throughout the year, write your git commits with valid markdown, making sure to link out to JIRAs, issues, etc
2) when you have something you think you'll want in the review at the end of the year, put a tag in the commit (e.g. eoypr)
3) at the end of the year just run this command:
`git log --author=me --after="January 1, 2017" --grep="eoypr" > review.md`
You can start adding additional tags to commits like, "[perf]", "[scaling]", etc. in case your company has certain goals you need to demonstrate you are hitting