First Bad Version
Explore how to determine the earliest bad version in a sequence where all subsequent versions are flawed. This lesson teaches you to efficiently use a modified binary search technique to minimize API calls while isolating the problem version. Understand the logic behind this approach and implement it practically.
We'll cover the following...
Statement
You are managing a product development team, and the latest release has failed quality checks. Because each version is built on top of the previous one, once a version is bad, every version after it is also bad.
You are given an array of n versions
You have access to an API isBadVersion(version) that returns TRUE if a given version is bad.
Your task is to find the first bad version while minimizing the number of calls to this API.
Constraints:
badn
Examples
Understand the problem
Let’s take a moment to make sure you’ve correctly understood the problem. The quiz below helps you check if you’re solving the correct problem:
First Bad Version
Given n = , if version is the first bad version, how many API calls are required to find it?
Figure it out!
We have a game for you to play. Rearrange the logical building blocks to develop a clearer understanding of how to solve this problem.
Try it yourself
Implement your solution in the following coding playground.
/* The isBadVersion(version) API is already defined for youwhich returns TRUE if a current version is bad. */public class Solution extends BadVersion {public Solution(int bad) { super(bad); }public int firstBadVersion(int n) {// Replace this placeholder return statement with your codereturn 0;}}