own experiences. There is no tool or method which could be applied to everyone. Pick those you think are the best fit for your own environment. I didn’t get any advantage out of those mentioned tools. It is pure my experience and favourites. Slides are focused for Ruby developers mostly.
notifications - Unwatch all irrelevant repositories - Create specific teams inside your organization: @backend, frontend, all, designers, po and so on.. This will help to tag people who can review or comment on your issue or pull request or participate in a general conversation. If you can’t mention specific team, tag/mention your colleague straightforward. - Add continuous integration service to your repository - Don’t merge PR until someone reviews it unless you really know what you’re doing.
+ Comments It’s a great way to review other developer’s code and immediately spot possible bugs. It also increases your code quality. Every pull request should be well tested!
and cloud infrastructure automation framework that makes it easy to deploy servers and applications to any physical, virtual, or cloud location, no matter the size of the infrastructure. getchef.com
to keep track of how your application behaves. It is a good practice to spot all errors before your customers do. There are several good tools which help to do so.
and trusted all around the world. Search your logs, create charts, send reports and be alerted when something happens. All running on the existing JVM in your datacenter. graylog2.org