The last few months I’ve been reading a lot about neuroscience behind learning and practicing music and I’m fascinated by the subject. It has helped me realise why the app works for me, as well as my own mistakes that held back my progress for many years despite putting in decent efforts.
It was a much needed inspiration to continue working on it with a re-evaluated roadmap.
Gerrit uses a “Change-Id” trailer with a unique value. When you “fix up” a commit, the commit SHA changes but the change id remains the same. That’s how it can identify different commits with the same change id as patchsets of the same change.
This is based on what I remember (haven’t used gerrit in a while), so it may not be accurate.
I used gerrit in my previous job and miss using it. Would definitely prefer it over GitHub which is more popular (and convenient of course, can’t deny that).
The last few months I’ve been reading a lot about neuroscience behind learning and practicing music and I’m fascinated by the subject. It has helped me realise why the app works for me, as well as my own mistakes that held back my progress for many years despite putting in decent efforts.
It was a much needed inspiration to continue working on it with a re-evaluated roadmap.
I recently wrote a blog post about it - https://www.captrice.io/blog/what-makes-captrice-work.html