Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a diagnostics folder? #103

Open
raq929 opened this issue Oct 17, 2016 · 3 comments
Open

Create a diagnostics folder? #103

raq929 opened this issue Oct 17, 2016 · 3 comments

Comments

@raq929
Copy link
Contributor

raq929 commented Oct 17, 2016

Move the creation of this folder from the https://github.com/ga-wdi-boston/unix-cli unit.

@raq929 raq929 changed the title Create a diagnostics folder Create a diagnostics folder? Oct 17, 2016
@gaand
Copy link

gaand commented Oct 19, 2016

I thought @J-Weeks handle this in unix-cli during a follow-along and had them move the folder into diagnostics after creating it.

@jrhorn424
Copy link
Contributor

It could be argued that basic command line should be part of the diagnostic. It's very chicken-and-eggy.

What about putting unix-cli as the first thing to learn, before completing the fundamentals-diagnostic?

I'm only putting this out there for consideration. I don't know what I prefer.

@gaand
Copy link

gaand commented Jan 6, 2017

Does this approximate what happens now?

  1. Clone and respond to fundamentals-diagnostic
  2. Squad assignments
  3. Unix CLI
    1. mkdir ~/wdi
    2. mkdir ~/wdi/trainings
    3. mkdir ~/wdi/diagnostics
    4. repeat for a bunch of directories
    5. mv ~/fundamentals-diagnostic ~/wdi/diagnostics

If so, I think I'm good with that. The fundamentals-diagnostic already takes an hour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants