Play the CLI Treasure Hunt

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, node.js, shell
Domain
cli, content

Research direction

Open the linked CLI-Treasure-Hunt coursework and follow the repository clone steps. Run node clue.js from the cloned folder, traverse the filesystem with Unix commands, and use the submission clue inside the treasure hunt to complete the activity.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Structuring-And-Testing-Data Submit:None
Link to the coursework

https://github.com/CodeYourFuture/CLI-Treasure-Hunt

Learning Objectives
  • traverse a filesystem using Unix commands
Why are we doing this?

Alongside learning JavaScript and Python, you need to become familiar with the basics of the command line. The command line is how you talk directly to your computer, instead of pointing and clicking at areas on a screen to trigger actions.

All interfaces are limited sets of possible interactions with data, arranged in ways (with words, colours, pictures, pixels) to guide the user towards the information they want. Clicking a link on a screen is really no different to typing cd Clues/Where . In both cases you are changing to a new directory. The difference is only in the interface you use to issue the command. Do not confuse the method with the goal.

I really want you all to understand this deeply and think about it many times over the course of your career. Do not decide you are "front end" or "back end" or limit your understanding in these ways. A CLI is an interface. An API is an interface. A GUI is an interface. All interfaces are maps. It's how we travel around data to find what we need.

The map is not the territory.

Maximum time in hours

1

How to get help

Share your blockers in your class channel.

How to submit
  1. Clone the repo from https://github.com/CodeYourFuture/Project-CLI-Treasure-Hunt
  2. Open the folder in VSCode
  3. Open the terminal inside VSCode
  4. Type node clue.js to start

The submission clue is inside the treasure hunt.

Anything else?

In the Beginning was the Command Line ~ Neal Stephenson, 1999

Dominant language
JavaScript
Stars
0
Forks
397
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Structuring-and-Testing-Data

All issues in CodeYourFuture/Module-Structuring-and-Testing-Data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.