243 karma · joined June 12, 2010
http://codingfearlessly.com
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.
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.
https://www.goodreads.com/book/show/3828902-thinking-in-syst...
Because even the best technology has people behind it.
I only meant situations where "80% there" (of the original plan) is enough and I certainly did not have in mind "fast and cheap" or "shortcut taking".
Thanks for taking the time to read and comment!
Also: it violates HN Guidelines (http://ycombinator.com/newsguidelines.html)
A couple of others on the back burner.
https://github.com/mmozuras/vim-github-comment/issues/3
I'm using fugitive myself - so I'll definitely consider interplay opportunities with it :)
https://github.com/mmozuras/vim-github-comment/pull/1 https://github.com/mmozuras/vim-github-comment/pull/2
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.
I just feel that people tend to pick these big frameworks, even when they don't need them. They just don't think about it and often dismiss these simpler tools. This talk came from someone saying to me 'oh, I started writing this <small-app>...'. And he spent the whole weekend basically just configuring all his chosen tools.
Thanks!
Two great suggestions, thanks!