Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

The reviewer is responsible for checking all 3 CTCI problems for correctness, test coverage, and readability. This can be the responsibility of one or more individuals.

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

A single member of the team will be responsible for presenting problems and solutions prepared for each session. Additional people can help as needed, but at least one person on the team will need to step in each week.

A single member of the team will be responsible for presenting problems and solutions prepared for each session. Additional people can help as needed, but at least one person on the team will need to step in each week.

The reviewer is responsible for checking all 3 CTCI problems for correctness, test coverage, and readability. This can be the responsibility of one or more individuals.

A single member of the team will be responsible for presenting problems and solutions prepared for each session. Additional people can help as needed, but at least one person on the team will need to step in each week.

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

The reviewer is responsible for checking all 3 CTCI problems for correctness, test coverage, and readability. This can be the responsibility of one or more individuals.

A single member of the team will be responsible for presenting problems and solutions prepared for each session. Additional people can help as needed, but at least one person on the team will need to step in each week.

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

A single member of the team will be responsible for presenting problems and solutions prepared for each session. Additional people can help as needed, but at least one person on the team will need to step in each week.

in string manipulation file for the function signature for problem 2,

#import <string>
using namespace std;

string englishInteger(int num);

should be

#include <string>
using namespace std;

string englishInteger(int num);

The reviewer is responsible for checking all 3 CTCI problems for correctness, test coverage, and readability. This can be the responsibility of one or more individuals.

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

The reviewer is responsible for checking all 3 CTCI problems for correctness, test coverage, and readability. This can be the responsibility of one or more individuals.

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!

Procedure for completing a problem & solution writeup for UWB ACM CTCI sessions:

• Assign an issue to yourself
• Pick a problem to write up. Please check the prior quarter's session to ensure we don't have duplicates between quarters. Some good places to look are LeetCode, HackerRank, and of course CTCI. Communicate with your colleagues to ensure we have good topic coverage and nobody is writing up duplicate questions.
• Clone this repository to your computer, if you haven't already. If you have, cd into the repo's directory, run git checkout master, and run git pull origin master.
• Run git checkout -b <my-topic-name>, and name the branch something logical. (Pick a short name for the problem you are writing up, for example.)
• cd into the directory with the solutions file for the session. The naming conventions should make the file's location fairly self-evident.
• Add the problem description in the appropriate numbered selection in the solutions file.
• Add the solution writeup in the appropriate numbered selection in the solutions file.
• Add a driver program (which includes your solution) in a subdirectory that produces the output included in the solutions file.
• Run git commit. Add a useful commit description, so that reviewers know what they're looking at.
• Run git push origin <my-topic-name>, using the branch name you chose earlier.
• Navigate to the GitHub repository and open a Pull Request for your submitted branch.
• Request a review from one or more designated PR reviewers for the session.
• If your reviewer requests changes, please address all suggestions.

As always, if you experience issues or have questions, talk to your peers. We are here to help each other!