More detailed instructions around making changes to a project in VS Code or Atom about software-interview-prep

[travisbartholome]

I can do this for Atom since it's what I normally use. Do you want this in a stand-alone .md file or as part of the README?

[LukeSchlangen]

Separate (in the supplemental-documentation) would be perfect! Probably a slight adjustment to the main README to link to it and encourage users to go there for more details. Thank you!

[izulien]

I am just setting up VS Code myself. I'll see if I can write up a supplemental document in a similar fashion to the one created by @travisbartholome.

If everything works as expected I should have a PR in later today or early tomorrow morning.

[LukeSchlangen]

That would be awesome @izulien! I'll reopen!

[izulien]

PR #24 Created.

[izulien]

@LukeSchlangen How do you want to reflect the VS Code Editor docs to the README?

Making your changes

Now that we have our own branch, we can make our changes. There are two ways to edit files, either in GitHub, or with a text editor on your computer. Open the file containing the code in a code editor. You can use any code editing program you are comfortable with, popular choices are Atom, VS Code, and Sublime Text.

See this document for more information
about using the Atom text editor to create new files and add them to the main lists of
interview questions. Even if you aren't using Atom, this document outlines the
general process for adding a new problem.

• We could put the link on the first paragraph at the mention of Atom and VS Code. Though users may think it links to their downloads sites.
• We could update the "See this document" line to simply reflect "See Using Atom or Using VS Code for more information about using a text editor to create new files and add them to the main lists of interview questions."

I believe the second bullet seems to make the most sense but I'll let you decide how you want the layout to fall.

[LukeSchlangen]

Good thinking. I think the second one makes the most sense too. If you want, you could add a statement about how, "People spend a lot of time choosing their favorite text editor, but don't get stuck here, Atom and VS Code are both great options, so we recommend simply picking one quickly."

The biggest concern I have with more choice here is putting people into analysis paralysis.

Do you want to add this PR or should I add an issue?

[izulien]

I can add it in. This project as a whole is helping me get more familiar with GIT in general. I just did a squash of my commits for my last PR.

I do agree, adding a "just pick one and go" type line would work pretty well.