search

tararoys / DBC_Sinatra_Skeleton

DBC's Basic Sinatra Skeleton
0 stars 0 forks source link

Sinatra Skeleton should not be a separate folder inside the DBC Sinatra Skeleton Folder #1

Open tararoys opened 10 years ago

tararoys commented 10 years ago

Instead, all of the files composing the sinatra skeleton should be in the root file DBC_Sinatra_Skeleton. It is ridiculous to go to DBC_Sinatra_Skeleton and move everything up one folder.

Sadly I don't know how to convince Git to move everything up one folder.

Actually, I did this once before: move everything up a folder, and now I don't remember where I stored that information. I think I saved it somewhere in a github repo on my computer. There are 200 github repos on my computer.

tararoys commented 10 years ago

Is it faster to

  1. Ask an developer?
  2. ask google
tararoys commented 10 years ago

Timeboxing learning how to grep on my computer to one repetition of Mars, Bringer of War.

tararoys commented 10 years ago

Experiment #1: Ask a developer: Me: "I am looking for an instructor who is enthusiastic about teaching me grep fu!" Four blank stares Me: "I'm trying to figure out how to grep recursively through files." 1: "Did you try googling recursively grepping through files?" 2: "Did you try man grep?" Me: "The problem is that in order to find the grep command I need I would need to know how to grep through the man page to find the command I need." 1: "There aren't that many flags are there?: Me: "....oh yes there are. The trouble with google is that everyone assumes I know enough grep to understand long-ass commangs 3: "In the man page, you can use "/", like the beginning of a regex, to search iterively through the man pages. do '/recursive' and I'll bet you'll find it.
Me: "/"? I didn't know that! I'll go try that!

Notes: The grep command is a needle. Google is a haystack. I find it demoralizing to be told to go back to the haystack to search for a needle when I'm pretty sure they could give me a specific useful answer.

Other note: Developers who are hiding in the corner get justifiably surly when someone comes interrupts their flow, in order to ask googleable questions.

Real question: how easy is it for a newbie to find the needle in the haystack?
How to we structure time and space so that newbies are not demoralized and developers are not interrupted?

Note: 

man grep

in the man page, type 

/recursive

This finds three instances of the word recursive in the man page, and higlights them black. They are not particularly easy to see, so I spent 30 seconds scrolling to find them. 

       -d ACTION, --directories=ACTION
              If  an input file is a directory, use ACTION to process it.  By default, ACTION is read, which means that directories are read just as if they were ordinary files.  If
              ACTION is skip, directories are silently skipped.  If ACTION is recurse, grep reads all files under each directory, recursively; this is equivalent to the -r option.
------------------------------------
       -R, -r, --recursive
              Read all files under each directory, recursively; this is equivalent to the -d recurse option.

Let me underline all of the technical terms I need to know in order to be able to search for the basic things I need to know:

Long story short: I need to know the technical terms I need to know in order to find the technical terms I need to know. That's not recursive, that's an infinite loop. No wonder my brain is constantly throwing stack level too deep errors.