FAQs

Frequently asked questions

Daily work impact

Q: Will this slow down our PR process?
A: No. We operate in parallel with your existing workflow and provide reviews within one business day. We're designed to be an additional reviewer, not a bottleneck.

Q: What if I disagree with the review feedback?
A: You maintain full control. Our feedback is advisory - we provide recommendations and explanations, but you ultimately decide what to implement. We encourage healthy technical discussion and will provide our reasoning and documentation where we can.

Q: Will this make me look bad if you find issues?
A: Not at all. Our role is to support and enhance, not criticize. We focus on constructive feedback and learning opportunities, similar to having a senior mentor.

Q: Do I need to change how I write or submit PRs?
A: No changes needed. Keep working in your normal workflow - we adapt to your processes and tools. Just tag us when you're ready for a review.

Technical concerns

Q: How technical is your feedback?
A: Very. Our reviewers are at minimum senior frontend developers who specialize in your tech stack, and provide detailed, implementation-specific feedback, including code examples and documentation links where appropriate.

Q: What if you suggest changes that conflict with our decisions?
A: You're the authority on your codebase. We'll explain our reasoning, but defer to your team's architectural decisions.

Q: How do you handle framework-specific patterns?
A: We study your codebase to understand your patterns and conventions. Our feedback aligns with your established practices while suggesting optimizations where valuable.

Q: Will this catch things that automated tools miss?
A: Yes. We identify code and component structural issues, performance optimizations, and maintainability concerns that automated tools can't detect. We also explain why things matter, not just what to change.

Team impact

Q: How does this affect team knowledge sharing?
A: We enhance it by working with you. Our reviews include explanations and documentation that become learning resources for the whole team.

Q: Won't this deskill our team's review abilities?
A: No - we complement internal reviews, focusing on frontend specifics while your team maintains ownership of architecture and business logic. We work alongside you as as impartial extra expert reviewer, we don't replace your internal knowledge base.

Q: How do you maintain consistency across different reviewers?
A: We maintain detailed documentation of your standards and patterns, and have internal quality processes to ensure consistent review quality. We have a single lead reviewer who has responsibility for each project and cycle through secondary reviewers to ensure knowledge is shared appropriately.

Q: How do you handle knowledge transfer?
A: Through detailed review comments, documentation, pattern libraries, and internal training sessions. We build a knowledge base specific to your codebase.

Process integration

Q: How do you integrate with our existing workflow?
A: We plug into your current tools (GitHub, GitLab, Bitbucket etc.) and processes. No workflow changes required.

Q: What metrics do you track?
A: We track:

Review turnaround time
Types of issues identified
Performance improvements
Code quality trends
Team satisfaction scores

Q: How do you handle urgent reviews?
A: Since we're located in New Zealand we've designed this service around providing overnight reviews. We don't prevent you from merging any code, so you are able to conduct urgent reviews without us. We can arrange emergency review coverage for Enterprise plans if needed.

Q: What's the onboarding process like?
A: A structured 3-week process:
Week 1: Setup and alignment
Week 2: Process calibration
Week 3: Full implementation

Strategic value

Q: How does this impact our velocity?
A: Effective code quality reviews typically improves team long-term velocity by:

Reducing technical debt
Catching issues early
Providing quick, actionable, actually useful feedback
Freeing developer time
Preventing quality-related delays

Q: What's the ROI?
A: Since we try to keep code repo permissions and pipeline access to a minimum we can't provide many direct metrics. However we encourage you to measure ROI through:

Reduced bug rates
Reduced cyclomatic complexity
Development velocity
Team productivity gains
Quality improvement trends
Better long-term understanding of frontend practices
Developer PR happiness

Q: How do you protect our IP?
A: We follow strict internal processes on handling any client data. We are happy to sign (and encourage you to provide) Non Disclosure Agreements if you require. We also defer to your secure access protocols, access management, and although we can provide a more effective service over the long-term if we understand business context, we can work with anonymized code if required.
We do store general notes about your code standards, architecture, and preference but that is only ever for internal use to provide a better service to you and is deleted upon any service termination.

Q: How does this scale with our growth?
A: Our service scales flexibly. Packages can be adjusted as your team grows, and we maintain knowledge continuity throughout scaling.

Risk management

Q: How do you ensure consistent quality?
A: We assign a single lead reviewer to each project who is responsible for consistency and continuity of service. We also regularly cycle secondary reviewers (under the lead reviewers guidance) to make sure there's always someone with deep context to take over. Aside from that we have:

Standardized review processes
Regular quality audits
We document your coding patterns/standards
Team training
Use automated tools where applicable

Q: What if the service isn't meeting expectations?
A: We want to deliver a high quality and professional service but we are human and still learning there will be areas that we can improve on. We're committed to adapting and improving based on your feedback.

Q: How do you handle security compliance?
A: We adapt to your security requirements and as much as feasible we work within your source control. We can:

Follow your security protocols
Use your access management
Work with anonymized code if necessary
Sign custom security agreements

We are also working towards SOC2 compliance.

Q: What happens if we need to pause the service?

A: You are free to pause the service at any time. Any unused time remaining from within that service period will be stored until you decide to resume again. Your data and account will also be kept as well as any long term use discounts you may have accrued.

Q: What happens if we need to terminate the service?
A: We strive to provide a clean, no hassle service. You are free to pause or cancel the service at any time. If you cancel within the first 10 calendar days of any service subscription period we will refund 50% of that period, after that there is no refund. Your data and account will be deleted after a short grace period as well as any long term use discounts you may have accrued. You will also be responsible for removing any users from your source control platform that may have been created during onboarding. If you wish to sign up again after cancelling you will need to create a new account and onboard again.

Product impact

Q: How does this affect our release cycle?
A: We work within your existing cycles and timelines. Our reviews are designed to catch issues early without causing delays.

Q: Can you prioritize feature-critical reviews?
A: Yes, we offer priority reviews for critical features and can align with your release priorities.

Q: How do you handle feedback about product functionality?
A: We focus on technical implementation while respecting product decisions. We'll flag technical concerns that might impact user experience.

Q: Will this improve our product quality?
A: Yes, through:

Better performance
Improved accessibility
Consistent user experience
Reduced technical issues
More reliable features

Technical concerns

Q: How technical is your feedback?
A: Very. Our reviewers are senior or above frontend developers who provide detailed, implementation-specific feedback, including code examples and documentation links.

Q: What if you suggest changes that conflict with our advice?
A: You're the authority on your codebase. We'll explain our reasoning, but defer to your team's ultimate decisions.

Q: How do you handle framework-specific patterns?
A: We study your codebase to understand your patterns and conventions. Our feedback aligns with your established practices while suggesting optimizations where valuable.

Q: Will this catch things that automated tools miss?
A: Yes. We identify component structural issues, design patterns, performance optimizations, and maintainability concerns that automated tools can't detect. We also explain why things matter, not just what to change.

Frequently asked questions

Daily work impact

Technical concerns

Team impact

Process integration

Strategic value

Risk management

Product impact

Technical concerns

Frontend Reviews

by Code Quality Labs