bitHound Blog

Now You're Speaking My Language

Most of us have been polyglots for as long as we can remember. Moving in and out
of languages is second nature and has allowed us to develop a signature set of
skills and a "flow" that we use to deliver our software.

However, introducing other individuals into the equation and forming a team
dynamic, can either complement the aforementioned flow or interrupt it.

The team's collection of skills, backgrounds and approaches should be celebrated
but if there is one language you and your team should all be speaking it is one
of quality.

One of our customers, Mathias Rangel Wulff shares his experience on the
importance of a common ground and understanding for teams when it comes to
software quality:

"I have been using bitHound for about 6 months now. Getting involved in a young open source project a few months ago, I quickly recognized how bitHound could become a truly valuable part of our team's workflow. The project we are working on, AlaSQL, is a JavaScript SQL database library for both relational and schemaless data. With AlaSQL, we have a strong focus on query speed and flexibility for datasources; so, code quality is an important step to ensure we achieve our goals. Also, because our team is comprised of many individuals, bitHound has become a natural way to ensure that we are all on common ground regarding the quality of our code. We have particularly appreciated the insights that bitHound provides pertaining to the broad range of objective issues to be solved. It's also very easy to share the state of the code with the team through the 'sharing' function or with a bitHound badge on the README file (we are on 74 - but we are working on it...). In using bitHound we have not only learned to code with a greater focus on longevity but now have a better understanding on where new members joining the project can contribute.

All in all, bitHound gives us the structure to configure a shared approach to linting, identifying complex code and ensuring that third party dependencies are up to date so we can all pull in the same direction towards the overall quality and health of the code base. We are very pleased with the service and can only recommend it. We would love to see bitHound dig even deeper with new ways of analyzing code as well as recommended ways to resolve issues so that JavaScript projects throughout the community can be assisted even more.

Mathias Rangel Wulff

It's imperative to be on the same page. Your team should have an understanding
of how quality is defined, the associated expectations as well as how quality
will be measured and vetted.

Your team should develop on stance on things like lint errors, security
vulnerabilities in third party packages and techdebt.

Shared style guides, pair programming and manual code review are great ways to
get your team moving in the right direction and very helpful for implementation.

Code-insight tools like bitHound can really augment the process by helping take
some of the tedious nature and guesswork out of the review process and provide
you and your team with objective evidence of issues impacting the code base.
Often times it's as easy as signing in with a GitHub or Bitbucket account.
Integration with these services also means you won't have to interrupt your
team's dev workflow.

So start establishing a common ground and understanding for code quality right
out of the gate and set your team up for great success!

Get started on bitHound with your team today!


How do you and your team stay on the same page? We'd love to hear from you.
Tweet us at @bithoundio

bitHound identifies risks and priorities in your Node.js projects.