To communicate isn’t just getting rid of syntax errors and making code work. The code should communicate ideas to people through a programming language that computers can also understand.
You should adopt semantic variables, classes, modules, and methods names. For instance, in Ruby, we avoid using particular prefixes such as is_paid, get_name and set_name. In their places, we use directly paid?, name, and name=.
My advice is to use idiomatic and features that the programming language you use offers to you whenever possible, and figure out ways to better pass the message.
Why wouldn’t we be worried about semantics, typos, and styles? We should care for the quality of our code, and the many concepts that define it. You can start by using a linter to collect some issues from your codebase automatically.
After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.
PullReview helps Ruby and Rails developers to develop new features cleanly, on-time, and with confidence by automatically reviewing their code.
RuboCop is a Ruby static code analyzer. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide.
Automated Git Updates- Nothing to install. Code Climate runs everytime you push a new commit.;Activity Feeds- Up-to-the-minute information so you can see when and how code changes.;Instant Notifications- Major security and quality changes pushed to where you work: email, Campfire, HipChat, and RSS feeds.;Team Sharing- Instant access for your whole team to maximize code visibility across projects.;Hotspots- A hit list for refactoring. Target your messiest areas one-by-one.;Duplication Detection- Fuzzy matching algorithm finds DRY-violations that human reviewers might miss.;Email Notification- Instant email notifications to let you know when new security and code issues arise;Security Dashboard- Organized listing of your app's vulnerabilities, including when they were first introduced and how to address them.;Alerts for New Rails Disclosures- Going beyond Gemfile analysis to let you know whether you're at high risk based on how your specific code uses a vulnerable library.;Start Fixing with One Click- Full integration with Pivotal Tracker, GitHub Issues, and Lighthouse lets you open tickets instantly.;GitHub Integration- Post-receive hooks for instant updates and GitHub drilldown links throughout.;Test Coverage Integration- Surfacing coverage information at the repo, class, and source listing level.;Private, Safe, and Secure- All data is private by default. SSL encryption everywhere.
Review of Ruby and Javascript;
Review on feature branches;
Review on integrations branches;
Detection of HotSpots;
Security checks;
Duplication checks;
Test checks;
Style checks;
Complexity checks;
Code Smells checks;
Design checks;
Notifications;
Customization per repository;
Team management and setup;
-
Statistics
Stacks
664
Stacks
7
Stacks
1.1K
Followers
496
Followers
65
Followers
222
Votes
285
Votes
70
Votes
41
Pros & Cons
Pros
71
Auto sync with Github
49
Simple grade system that motivates to keep code clean
45
Better coding
30
Free for open source
21
Hotspots for quick refactoring candidates
Cons
2
Learning curve, static analysis comparable to eslint
