1

Codacy Product Showcase: April 2024

Group 370
2

Codacy Security Adds Thousands of New SAST Rules With Semgrep Integration

Group 370
3

All Case Studies  ·  Stim

Stim

250% increase in coverage with Codacy

stim-3

 Industry: Media & Internet 

 Location: Stockholm, Sweden

  Solutions

Icon 1

Codacy Quality

Icon 1

Codacy Coverage

|  Challenge:

Stim needed to modernize the technologies used to replace legacy systems, which included rewriting and refactoring portions of code and completely changing the programming languages used.

|  Value:

Stim was able to increase test coverage for their code across 80 applications from 23% to 64% with Codacy.

|  Employees:  153    ·     Website: www.stim.se

Lorem ipsum dolor amet, consectetur adipiscing 

Lorem ipsum dolor amet, consectetur adipiscing
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim.
Get Started

200+

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

 

200+

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

 

200+

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

 

Icono-Bocadillo

"When we started measuring things, on average, we were at 23% coverage of the 25-30 applications that were covered. We now have 80 applications with test coverage, and the average test coverage has gone up to 64%."

tobias-sjosten

Tobias Sjösten

 Head of Software Engineering

Making Sure Your Code Withstands The Test Of Time

Stim Customer Story 

About Stim

Stim is a collection society of composers, authors, and publishers, with over 100,000 members and music publishers. Since 1923, they’ve been working for solid copyright protections and guaranteeing their members get paid when their music is performed, streamed, played in public, or used in TV and film.

The main programming languages used by the Stim development team include Go and TypeScript. In addition, they use GitHub as their version control system. Stim employs a hybrid solution, hosting on CGP and on-premise servers.

Challenge

Much of the code Stim developers need to work with was written in the 1980s in IBM RPG, a programming language that only a few people know nowadays. As such, Stim needed to modernize the technologies used to replace legacy systems, which included rewriting and refactoring portions of code and completely changing the programming languages used.

At the same time, Stim must stay competitive in the music world and keep evolving and creating new applications.

“We’re building new applications to take over functionality from the old systems. (...) But we are constantly trying to keep things up-to-date and modernized, with this delicate balance between staying agile, having the latest technology, and taking care of the old systems," said Tobias Sjösten, Stim's head of software engineering. 

“The things we build must have a high quality because they will be around for a long time. They have to endure and be well-built so that they can stick around for decades to come.”

With Codacy

In several organizations, legacy code also means that, besides the technological gap, developers wrote the code without tests. Code coverage, however, is vital to improving software quality by lowering the chances of releasing code with undetected errors and bugs. 

“When we started measuring things, on average, we were at 23% coverage of the 25-30 applications that were covered. Since then, that has grown; we now have 80 applications with test coverage, and the average test coverage has gone up to 64%. So it’s been tremendous growth in how we are testing our applications,” Sjösten said.

As a general rule, the new code cannot introduce any new issue. Plus, the feedback given by Codacy Quality is used to improve already existing code. So Stim implemented a triage process to address those issues, improving their code quality. In this process, one person per team is on triage duty, where they spend some time looking at critical issues and deciding if they’ll fix them now, if it’s something they shouldn’t fix, or if they should create a ticket about it.

“Your [Codacy’s] issue detection has been very enlightening because some older applications had something like 43,000 critical issues. It’s impossible just to pause everything and fix all the issues. So we implemented something we call triage (...) We have seen that the issues vanish in the teams who have been good at it. And the code quality is very good. Just having this practice again has lifted us, and that was thanks to Codacy because Codacy identified it and gave us a useful list to prioritize," Sjösten explained. 

Future

The next step for Stim is to expand their usage of Codacy Quality and better configure the platform for their needs. They also recently started using Codacy Pulse. 

“I’m super curious about Pulse because this year our KPIs are the DORA metrics. So that will be very interesting to look at as well," Sjösten said. 

“It’s great to see how your product keeps developing as well. That gives me some safety that we picked the right product as well. You keep developing things, and much of what you develop is in the direction that I would like to see as well. So that’s great,” Sjösten added. 

We look forward to seeing what Stim accomplishes in its mission of influencing policies and working for diversity and re-growth in the music industry.