<commit_before># interview-problems
Collection of interview problems.

## Why?
As a software developer, usually the second step of a job interview is a coding
challenge (being the first step a simple screening call). According to my
experience, most of these interview problems are algorithm-based, logical
problems you need to solve in a certain period of time. This reposiroty will
serve as a dump of logical questions I was asked or fun challenges I found
around the web. I’ll also try to include solutions (usually mine), but I cannot
guarantee they will be correct or performant. `</disclaimer>`

## Guidelines
```
/problem-name-folder
├─ README.md
├─ solution.js
└─ test
    └─ test.js
```
- The diagram above describes the base structure for a problem.
  + `README.md` will have the code challenge statement, explaining the problem
    and asking for the solution.
  + `solution.js` will contain the JavaScript solution of the problem,
    structured in a way that [Mocha](http://mochajs.org) can use.
  + `test/test.js` is a [Mocha](http://mochajs.org) test file, where you can
    test the solution and describe the outputs you might be expecting for
    certain inputs.
- Main solution always in JavaScript (runnable with Node.js).
  + You can add solutions in other languages, though.

## Wanna help?
Do you have a great/fun/wacky interview problem you would like to share with
the community? Fork this project, add you challenge (following this
[project’s guidelines](#Guidelines)), and submit a pull request! I promise to
check it out as fast as possible and accept it. :smiley:

## Todo
- [x] Yeoman generator
- [ ] Talk about & link yeoman generator
- [ ] Fix yeoman generator to create the folder with the name provided
- [ ] Check the message:  
      `(!) #mkdir() is deprecated. Use mkdirp module instead. https://www.npmjs.com/package/mkdirp`<commit_msg>Small readme update.<commit_after># interview-problems
Collection of interview problems.

## Why?
As a software developer, usually the second step of a job interview is a coding
challenge (being the first step a simple screening call). According to my
experience, most of these interview problems are algorithm-based, logical
problems you need to solve in a certain period of time. This reposiroty will
serve as a dump of logical questions I was asked or fun challenges I found
around the web. I’ll also try to include solutions (usually mine), but I cannot
guarantee they will be correct or performant. `</disclaimer>`

## Guidelines
```
/problem-name-folder
├─ README.md
├─ solution.js
└─ test
    └─ test.js
```
- The diagram above describes the base structure for a problem.
  + `README.md` will have the code challenge statement, explaining the problem
    and asking for the solution.
  + `solution.js` will contain the JavaScript solution of the problem,
    structured in a way that [Mocha](http://mochajs.org) can use.
  + `test/test.js` is a [Mocha](http://mochajs.org) test file, where you can
    test the solution and describe the outputs you might be expecting for
    certain inputs.
- Main solution always in JavaScript (runnable with Node.js).
  + You can add solutions in other languages, though.

## Wanna help?
Do you have a great/fun/wacky interview problem you would like to share with
the community? Fork this project, add you challenge (following this
[project’s guidelines](#Guidelines)), and submit a pull request! I promise to
check it out as fast as possible and accept it. :smiley:

## Todo
- [x] [yeoman generator](https://github.com/gnclmorais/generator-interview-problems)
- [ ] Talk about & link yeoman generator
- [ ] Fix yeoman generator to create the folder with the name provided
- [ ] Check the message:  
      `(!) #mkdir() is deprecated. Use mkdirp module instead. https://www.npmjs.com/package/mkdirp`
{'fraction_non_alphanumeric': 0.08095362850406078, 'fraction_numerical': 0.0, 'mean_word_length': 4.043593130779392, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 3, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3537002', 'n_tokens_mistral': 1064, 'n_tokens_neox': 1024, 'n_words': 529}