.svg)
We have talked with Felipe Adorno, CTO at Monkey Exchange, to better understand what made the company opt for an automated code review tool like Codacy, the benefits he and his team found, and what it helped them solve. Monkey Exchange uses Java as its primary programming language.
About Monkey Exchange
Monkey Exchange is an online corporate financial alternative to SMBs in Brazil, focused on reducing the cost of capital. The company, which was founded in 2016, aims to provide financing to a company’s supply chain using receivables exchange, and it does this by linking suppliers to buyers in a competitive environment. The company offers prepayment of receivables from large corporations, such as Gerdau, Saint-Gobain, Fiat Chrysler, and Usiminas, to a large number of suppliers.
Q. What were your company’s main needs that led to implementing Codacy in your company?
At first, we had another tool running in our infrastructure and the team lost quite a few hours monitoring, updating, and maintaining. With Codacy, we only needed to configure the repository once and only care about our code quality.
Q. While using Codacy, were you surprised with any particular benefit that you did not expect?
The main benefit we get when we change to Codacy is the detailed dashboards, the main overview is a pinned page in my browser, and I can see the metrics of all projects and of opened pull requests this is amazing.
Q. What were the main issues you tried to tackle with Codacy and why? Can you tell us how much you improved the main issue you had?
Everyone in our developer team is a user of Codacy and we are impressed with the commitment and with the quality of the test coverage, which has been increasing. This is a major concern for developers when writing or changing any part of our codebase.
Q. Why did you choose Codacy instead of another tool?
Any development team needs a tool to automatically check the code quality, and the tool needs to be simple, intuitive, and easy to configure. In our opinion, Codacy has it all, so we decided to use this great tool.
Q. Can you provide me with the Codacy solution you decided to implement and why? Is it cloud or on-prem? How many seats? What Git provider do you use and why?
We chose Codacy on Cloud because it is ready to use and we don’t need to care about maintenance and upgrades. Today we have 9 spots and this grows with our team. We use GitHub because it is secure and trustworthy.
Q. Can you compare how your workflow is today with how you were working in the past?
In the past, all of our Pull Requests were revised only by our team members, and now we wait for Codacy to check and validate the quality of the Pull Request: when Codacy is green we release the Pull Request for our team members to review.
Felipe Adorno is the CTO & Partner at Monkey Exchange, where he works heavily with Spring Cloud and has over 10 years of experience in the technology world. He is active in the Java community, where he has always given lectures and participated in debates on the most varied subjects. In addition, he has contributed to some frameworks such as Apache Commons, FF4J, Netflix Ribbon, and others.
Thank you Felipe, for sharing these insights, and use case with us!
If you’d like to hear more from our customers, you can read our clients’ stories here. To learn about Codacy and our plans, please visit our page, with the pricing and breakdown of both Pro (Cloud) and Self-hosted plans.
