CUSTOMER STORY

Improving Game Development with Gitential

Share on facebook
Share on twitter
Share on linkedin
Share on reddit

IN THE SPOTLIGHT:
Pocket Piñata Interactive

Chris Khoo
Chris Khoo

Founder and CEO/CTO

HQ: Vancouver, Canada
Founded: 2011
Size: 5-7 Developers
Market: Mobile, PC, Console, and Web Software Games

With 24 years of software engineering experience, Chris Khoo has forged a distinguished development studio responsible for producing numerous prestigious gaming titles like FIFA and The Sims.

Pocket Piñata Interactive is a distinguished mobile game development studio. They offer end-to-end game production including client and server programming, technical design, art production, game design, telemetry design, and analysis.
Their portfolio includes award-winning AAA franchises such as FIFA, Need for Speed, The Sims, Dragonvale, Club Penguin, and Lego, to name a few.

THE CHALLENGE:
Deployment Deadlines Compromised

Chris recently needed to face some challenges when a project fell behind his roadmap and timeline estimations. It happened despite the fact that one of their best performer architects were leading the project. Chris was not able to foresee the situation which made it impossible the prevent missing the deadlines.
That was the time, he felt he needed to look up some data to deep dive into the situation.

THE SOLUTION:

Chris noted that since they started using Gitential, he pays very close attention to coding hours, churn, and code volume.

Thanks to the tool, he was able to rapidly identify major efficiency problems with a lot of code being rewritten causing high churn rates.

Chris noted that since they started using Gitential, he pays very close attention to coding hours, churn, and code volume. Thanks to the tool, he was able to rapidly identify major efficiency problems with a lot of code being rewritten causing high churn rates. Upon deeper examination, most of the code churn was concentrated in Android files written by a specific developer.

What caused the problem?

In a case like this, Chris needed to talk with the developer to find out what was going on. As it turned out, though the architect was one of the team’s best Unity developers, this was the first time he wrote anything in Android Studio. He didn’t think it would be a problem to learn a new tool while working on the project. Nevertheless, his lack of experience led to trying out different solutions with frequent rewrites, ultimately impacting product delivery.
Using Gitential insights he managed to find where he needed to look for the root cause and found a solution.

LESSON LEARNT:

There’s the old adage of “Trust, but Verify.” This scenario underscored that even very experienced, high-performers can have skill gaps. Sometimes they are reluctant or hesitant to admit they lack experience or skills outside their areas of specialization. They might also be overly optimistic about being able to learn a new language on the fly.
Knowing there’s a skill gap enables managers to arrange supplemental training, assign smaller or easier tasks, assign an appropriate mentor, or a code review partner.

About Gitential

Gitential is an Analytics and Engineering Intelligence service provider bringing visibility and optimization highlights on teams’ productivity. Our mission is to enable faster, data-driven decisions to continuously improve software delivery team cost performance and proactive risk management.

Ready to explore different ways to improve your software projects’ efficiency? Schedule a meeting and we will be happy to listen to and discuss your needs.

Have a project but are not quite ready to contact us? See if Gitential is a fit for you!

FREE TRIAL FOR LIFE
for up to 5 repos, 10 devs and 3 months of data

You might also enjoy

How to Notice and Prevent Software Developer Burnout

How to Notice and Prevent Software Developer Burnout

How do you notice and prevent software developer burnout as a team lead or engineering manager? Burnout affects each person a bit differently. It often starts subtly and progresses incrementally. Developer burnout feeds into a vicious loop that can make your developers quit or even change career path. If not corrected, it can also lead to health consequences. The good news is that its onset can be identified, prevented, and rapidly alleviated. Let’s examine how.

Read More »
Effective Code Reviews

Best Practices for Effective Code Reviews

More than half (53%) of the software development teams do code reviews on a daily basis, according to SmartBear’s 2019 State of Code Review. They find, as one would expect, that more frequent code reviews have a direct correlation to higher-quality code. As their report goes on to say, “There is a compounding effect when you introduce all the benefits of code review into daily behavior. Communication improves, knowledge about the codebase is shared, and fewer bugs make it through development to QA.”

Read More »
Code Churn: The Good, The Bad and the... Perfect

Code Churn: The Good, The Bad and the… Perfect

Code churn is regarded by many software engineers as the best indicator of a code’s quality and defect density. Most engineers will also agree that code churn is good or bad relative to when and why it is taking place. But it is worth understanding in detail because it is 100x less costly to catch a defect during the design phase than catching it during maintenance.

Read More »

Did you like our content?

Spread the word

Share on facebook
Share on twitter
Share on linkedin
Share on reddit

Subscribe to Our Newsletter

Don't miss our latest updates.
All About Software Engineering Best Practices, Productivity Measurement, Performance Analytics, Software Team Management and more.

Did you like our content?

Spread the word

Share on facebook
Share on twitter
Share on linkedin
Share on reddit

Subscribe to Our Newsletter

Don't miss our latest updates. All About Software Engineering Best Practices, Productivity Measurement, Performance Analytics, Software Team Management and more.