One of the biggest motivations for building Trici has been the perceived impact it will have on improving the lives of open source developers.
Many contributors to open source software contribute because of their interest and passion and not because it's their full time job. This leads to a scenario where they do not always find continuous chunks of uninterrupted time to work on their favorite open source projects. For example, you may work on fixing bugs reported on your open source library, only in the evenings or on weekends. It is not necessary that you are able to finish fixing a bug in one sitting. Maybe the changes that you made to fix the reported bug lead to other regressions, but it's already late in the evening and you have to sleep. Next evening, after a day at work, when you resume fixing the bug, it will take a certain amount of time (typically 5-25 mins) for you rebuild your train of thought and continue working. However, by using Trici, you can review last evening’s focus session and this rebuilds your train of thought very fast (typically less than 60 seconds) This saves you time and thus you are able to get more done.
Another scenario that is common in open source software development is the asynchronous nature of feedback. For example, let's say you made some changes and raised a pull request. It is not necessary that your changes will be reviewed on the same day. In fact, for some projects the review may take a week or two. The reviewer may ask you questions about why you took a certain approach but you may not exactly remember the reason. A real example of such a scenario can be seen below in the github comment.
With Trici, you can search and review the specific focus sessions and remember what you had done in a matter of minutes. These are a couple of scenarios specific to developers contributing to open source where Trici could be useful. Are there any other scenarios that you can think of?