Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That can be tricky. You should consider writing specifications for your work/role that:

- Are labeled with the name of the task: R&D; Solving Scaling

- Indicate what's improving over time and what the general workflow involves

- Show how you personally track that progress in a log or other methods

- Help you demonstrate that you are qualitatively improving the situation

(- Over time: Develop into some helpful metrics you can measure, as you make observations about these systems)

In such cases it usually helps to give reports in a linear narrative format. Other reports, e.g. quantitative reports on qualitative work, probably won't do your work justice for now. But that just means you use a different lens to examine or present the work.

If it's nothing of note, at the bare minimum it should be presented contextually as an organized part of a broader/longer narrative (even if you need to summarize the narrative).

Good luck.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: