That insight gave me more confidence. Before 'Quiet', I wouldn't allow myself to act a certain way or would feel bad if I did.
One simple example: as an introvert, I would get tired at parties or gatherings of bigger groups.
Before 'Quiet', I would try leave unnoticed (slightly embarrassed from leaving so early). Or I would stay and feel increasingly worse.
Now I'm better aware of what's going on inside me. I feel more confident and leave. Or I find a quiet corner, read a book on my iPhone for 20 minutes, and get back to the group.
Quiet: The Power of Introverts in a World That Can't Stop Talking
My favorite book in 2013 (http://codingfearlessly.com/year-2013). After reading it, I accepted my introversion and learned how to better use it, view it as a strength instead of weakness.
* Enable smaller PRs. Reviewing 50-150 lines of code is much less daunting. This can be done by using tools like feature flags, AB tests, github/scientist etc.
* Ask/communicate about the quality of PRs. Like: splitting big ones into multiple,writing good descriptions, including the problem and screenshots.
* Automate the trivial parts. We use Pronto (disclaimer: I'm the author - https://github.com/mmozuras/pronto), but there are other tools/services that can help achieve the same result.
Currently, my main side-project is Pronto, quick automated code-review tool: https://github.com/mmozuras/pronto
Intend to make a SaaS from its current library form, at some point, also.
You're absolutely correct - and the reason I did it that way: easier to accomplish for the first version. I have the intention to take a stab at implementing inline comments, but it's not that simple. For comment to be inline, a line index in the GitHub diff has to be specified. More information about that particular API method: http://developer.github.com/v3/repos/comments/#create-a-comm...
You can delete these kind of comments by clicking "Show lines notes below" checkbox and proceeding from there.