1

Watch our latest Product Showcase

Group 370
2

Meet us at WeAreDevelopers World Congress in Berlin

Group 370
3

Spotlight Whitepaper by IDC on Importance of Automated Code Review Technologies

Group 370

July Product Update 🚀

In this article:
Subscribe to our blog:

Hi there đź‘‹,

We hope you’re having a great time over the holidays if that’s your case 🏝 Either way, your friends at Codacy wish you a wonderful week!

Here are a few updates from July that we’ve been working on. There’s also a new webinar that you don’t want to miss, so keep on reading!

Improving Coverage experience

sshot-settings-coverage

We’ve been working hard to make the experience with our coverage features more enjoyable for you. Our product squads have been focusing on:

  • Fixing bugs;
  • Increasing the stability of our system;
  • Improving the existing features: better visibility of coverage errors, an enhanced granularity of coverage metrics, and the possibility of seeing coverage updates on PRs, among others.

All this invisible work will become visible to you soon!

Pylint updated to version 2.14.5

Pylint 2.14.5

We just updated the Pylint tool to version 2.14.5 (the last stable version). The tool checks your Python code for errors and warnings, helps enforce a coding standard, sniffs for code smells, and offers simple refactoring suggestions.

Check out the entire list of all supported languages and tools.

Generate Checkstyle config files with Codacy Labs

Checkstyle configuration files

Codacy Labs is a place where we do some experiments using the Codacy API and a web client to fulfill specific requests from some of our customers.

Our Solution Engineering team developed a solution that generates a configuration file based on your coding standards, and you can then use the file in your IDE. This was previously only available for PMD, but we now added Checkstyle as well!

Next Webinar: Maintaining Code Quality in Open Source with Niels Lohmann

Talk - Maintaining Code Quality in Open Source

Join our guest speaker to learn how to maintain code quality in an open-source project that keeps growing.

Niels Lohmann is the founder of JSON for modern C++ on GitHub, currently used by Apple, Microsoft, Google, Volkswagen, and Daimler.

Live talk: This is how we accelerate with quality engineering

This is how we accelerate with quality engineering

We had a live talk with the guest speaker Antoine Craske, Director of Architecture & Technology at the international retailer La Redoute.

In case you missed the talk, don’t worry, you can (re)watch the recording here. Short on time? Check out the highlights from the talk in our blog.


Careers at Codacy: We’re Hiring đź¤©

We’re hiring for our Engineering (Backend, Frontend, SRE), Product, Customer Success, Sales, Marketing, Support, and People Teams. All remote positions – join us from anywhere in Europe and help us do awesome things! Check our current openings.


Interesting reads 

Code reviews: the essential guide [ebook] đź“š

Code reviews are one of the most important aspects of today’s software development workflow. That’s why we created a guide that explains in detail what code reviews are and how to optimize them. We even give you checklists to help you become the best code reviewer you can be. Read the ebook → 

“How to Misuse DORA DevOps Metrics with Bryan Finster” by CantonCoders 🧑‍💻

Have you been using DORA metrics but feel that your development is not going as fast as expected? Learn that these metrics are part of a more complex process, and although they are extremely important, they are only the tip of the iceberg. Watch the video →

“10x developers really exist” by David Saltares 💪

“Since the original 1968 article â€śExploratory experimental studies comparing online and offline programming performance”, there has been a lot of debate around the figure of the 10x developer. We’re talking about engineers who are an order of magnitude better than their peers by whatever measure. These engineers exist, but not in the way most people describe them.” Keep reading here →

“Three Tips for Managing Technical Debt: While Maintaining Developer Velocity (and Sanity)” by Adi Belan 🙌

Technical debt happens because developers favor a “quick and dirty” over a more polished and clean solution to reduce the overall implementation time. But there are ways to manage tech debt, and Adi Belan from AppsFlyer shared three tips on how to do it. Check them out →


Community

We are more than 500 members in our community! đźš€

Your support and feedback are very important to us, and we look forward to keep growing and learning with you. Thank you all 🙌 👫

Top Community Users July 2022

Give feedback on our Roadmap

We’d like to continue sharing our roadmap with you ✨ You can see what’s in progress, and what’s up next. You can also submit an idea/feature request and vote on what is most important! Your feedback matters 💪

See what’s next →


If you think this content is relevant to you we would be extremely happy to send it over to you every single month. Feel free to subscribe below and welcome on board! ⛵

RELATED
BLOG POSTS

September Product Update 🚀
Hi there đź‘‹,
October Product Update 🚀
Hi there đź‘‹,
June Product Update 🚀
Hi there đź‘‹,

Automate code
reviews on your commits and pull request

Group 13