Extract the utility (eg. Facebook’s events and groups) without getting sucked into the cycle of shallow dopamine hits that is the news feed.
33 karma · joined February 25, 2013
github.com/cpjk
[ my public key: https://keybase.io/cpjk; my proof: https://keybase.io/cpjk/sigs/aqqK7c248eSVuzcwQ4GETy-ejCGixYve__tfY1As1AY ]
Extract the utility (eg. Facebook’s events and groups) without getting sucked into the cycle of shallow dopamine hits that is the news feed.
Obviously being an asshole is out of line, and if someone is being a dick in code review, that's a problem with the reviewer. But I think that being rigorous about maintaining consistency and quality is important.
Having now worked at other places where code review is given low priority, I can say with confidence that I don't want to work anywhere that does not do serious code review.
Code review provides an important mentorship opportunity for junior programmers, and provides a simple way to keep code quality high and consistent. In addition, it provides a simple way to instruct new hires on internal style and conventions.
However, I feel like the thing holding me back from leaving vim is its customization. I like to work with multiple vim and tmux splits side by side, e.g. dev server output on one tmux split, with vim splits inside another tmux split looking at the server code.
Most IDEs I've tried more or less force a workspace layout on me, and might make it hard to achieve something like that. However, I can see that, depending on your preferences and area of work it can be a reasonable trade-off.