Talk
The Challenges of Code Quality and Team KPIs in a Monorepo at JS Poland
Description
How to get the right numbers on every PR?
In bigger mono-repos, management as well as development often struggle to integrate the right metrics. The need spans from having an easy to communicate number, over to actionable feedback on the line of code. I share my learnings of working on, migration and improving large scale repositories and how to track the progress and quality of it.
Takeaways
Learn about the technical challenges:
aggregate code coverage
split linting into quality and development
keep performance and scalability regression free
Understand the benefits of automations:
visibility of progress
speaking numbers
consistency in historical data Stop running blind! Get the right insights on every PR.
ngPoland 2024 - Code Quality and team KPIs in a monorepo
More from the speaker
Modern Angular Best Practices: Reactivity and Resource Based Architecture | @NgGlühwein
PushBased
Dec 11, 2025 · Vienna, Austria
Advanced CPU Profiling in Node - Profile Data Structure
CPU profiles are more than flame charts—they’re structured JSON files. Learn how nodes, samples, and time deltas form the backbone of DevTools performance data.
Advanced CPU Profiling in Node - Real-Life Examples
Profiling is easiest when it's real. Learn how to capture and make sense of CPU profiles in Node.js across scripts, threads, and processes—then apply it to your own projects.
Advanced CPU Profiling in Node - Best Practices and Pitfalls
Get deeper insights into your Node.JS performance. Learn how to master advanced CPU profiling with built-in tools, interpret process/thread IDs, and optimize using sampling intervals. Troubleshooting and real examples included.
Implementing Incremental Hydration in Angular (Part 3/3)
Implement incremental hydration in a real-world Angular app - Basic setup, hydration triggers and important considerations for a seamless integration.
The Game-Changing Impact of Incremental Hydration in Angular (Part 2/3)
Let's dive deeper into why incremental hydration in Angular matters so much for performance and user experience, focusing on its influence on Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).