I use CodeFactor.io because my school team is really intense about being as professional as humanly possible before going into the industry. We find it is a great way to force people to think about the complexity of their functions and remember certain things we don't often think about (explicit single param functions!).

Unfortunately, we had to make it not a required check due to a large amount of false positives. There have been many pull requests where it will report reduced code quality because a function near the code that was changed was already poor quality (from before code factor was added). It's not really feasible or the responsibility of the person doing that specific pull request to fix what is likely someone else's mistakes.

It also has a problem with switch statements that are simply enum conversions. We often have a use for stringifying enums, but it will say there are "18+ code paths", which makes it a complex function. We're more than fine with this and the solution of using an unordered map isn't really elegant.

We've also gotten a fail because "Complex Code" and it just points to the whole file. Like...okay? What do you want from me? How do I help with this? "The file just kinda sucks". Thanks CodeFactor.

I would also really like the ability to ignore something that comes up during a pull request. Doing so doesn't make the code factor check pass. I'm not even sure if I have the option to do that.

I use CodeFactor.io because it really does help my team to find problems in our code. Its a really valuable extra step in our review process that points out things that need to be simplified or code that is repeated from somewhere else in the project. It makes our reviews more efficient and can catches style problems that are tough to catch any other way (until they bite you).

I use CodeFactor.io because it has helped me create a habbit of conforming to PEP8 when writing Python. It has drastically improved the overall quality of my code base on its way into production. Combined with other CI/CD tools, it is a great way of working in best practices into my development process.

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

It is very important to have clean code. To be sure that the code quality is not really bad I use a few tools. I love SonarQube with many relevant hints and deep analysis of code. codebeat isn't so detailed, but it can find complexity issues and duplications. Codacy cannot find more bugs then your IDE. The winner for me is SonarQube that shows me really relevant bugs in my code.