Need advice about which tool to choose?Ask the StackShare community!
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.
Pros of Phabricator
- Open Source33
- Code Review29
- Supports Git/Hg/SVN25
- Bug Tracking18
- Audit Source Code17
- Unlimited Repo Support11
- Software Engineering Platform10
- Super fast task creation10
- Flexible Project Management9
- Project Management8
- Self hosted5
- Building Better Software4
- Best Integration with Gitlab2
- Complete set for collaborating on software development2
- Powerful, Complete, Fast, Reliable and Open Source1
- Straightforward code review process1
- Workflow1
- Very effective system, does all PM & code org needed1
Pros of Phacility
Pros of RuboCop
- Open-source9
- Completely free8
- Runs Offline7
- Follows the Ruby Style Guide by default4
- Can automatically fix some problems4
- Customizable4
- Atom package2
- Integrates with Vim/Emacs/Atom/Sublime/2
- Integrates With Custom CMS1