Is AI actually helping your engineers?

Twelve situations across six dimensions. About six minutes. Scored in your browser — nothing is sent anywhere until you choose to send it. There is no pass mark.

Scoring this needs JavaScript. Email your answers to connect@coderewired.com and we will send your score back.

Tools

Q1

Which AI coding tools does your team use day to day?

ANone yet, or everyone picks their own with no visibilityBOne tool, used inconsistently across the teamCOne or more tools, used by most of the team

Q2

How are AI tool licences and access managed?

AIndividuals use personal accountsBIT provisions seats, but there is no usage policyCSeats are provisioned and governed by a written policy

Review

Q1

When a pull request contains AI-generated code, how is that flagged for the reviewer?

AIt isn't, and reviewers usually can't tellBSometimes mentioned in the PR descriptionCAlways labelled, so reviewers know what they are reading

Q2

How has review time changed since AI tools arrived?

ANoticeably longer, and we have not adjusted the processBLonger, and we are aware of itCAbout the same, because we changed how we review

Testing

Q1

Does AI-generated code get the same test coverage requirements as hand-written code?

ANo formal requirement either wayBExpected, but not enforcedCEnforced in CI

Q2

How confident is your team that your test suite would catch a subtly wrong AI-generated change?

ANot confidentBSomewhat confidentCConfident, and we've seen it happen

Delivery stability

Q1

Has your deployment frequency or change failure rate shifted since adopting AI tools?

AHaven't measured eitherBMeasured once, not tracked over timeCTracked continuously, and we review the trend

Q2

When something ships broken, can you tell whether AI-generated code was involved?

ANo way to tellBSometimes, from memoryCYes, it's recorded

Governance

Q1

Is there a written policy on what AI tools may touch — code, customer data, secrets?

ANo written policyBInformal guidance, not written downCWritten policy, communicated to the team

Q2

Who is accountable when AI-written code causes a production issue?

AUnclearBThe engineer who merged it, by defaultCDefined as part of the review process itself

Skills

Q1

Have your engineers had structured training on reviewing AI-written code?

ANoBInformal, peer-ledCStructured, with a defined method

Q2

Can your engineers explain why they accepted or rejected a specific AI suggestion?

ARarelyBUsuallyCAlways — it's part of how we review

1 / 6

Your result

0 / 24

Where to focus first

Book a 30-minute call

Send this result

Optional. Nothing leaves your browser until you agree and send.

I agree to send this result, with the scores above, to Code Rewired.Email my result

Or start with the free AI coding policy template. Related reading: measure adoption, rollout plan, review checklist, context engineering.

code rewired

Architecting your transition to AI-native development.

AI engineering adoption for software teams: measured, not hyped.

[email protected]

Readiness Pricing About Work Insights Policy template Talk to us

Case studies

SwiftCause EaziCore YNV Solutions

Follow the build

YouTube
LinkedIn
X
Instagram
Facebook
GitHub

Privacy Cookies Terms

AI ADOPTION / CODE REVIEW / DEVELOPER TOOLSArchitecting your transition to AI-native development.

We’d like to use PostHog analytics cookies to understand how people use this site, so we can improve it. They’re only set if you choose Accept. Cookie policy

Cookie categoriesEssentialAlways on — stores this choice onlyAnalyticsPostHog, EU-hosted