Here's a shortlink to this page: http://bit.ly/WDI5_DC_InstallFest
Please follow these instructions in order.
Open Applications > Utilities > Terminal
Robin (Robert) Thomas RobertAKARobin
We, the Impossible Missions Force, have become aware that Doctor Nefarious is planning on using his Nefarious Computer (a standard Macbook) to initiate a nuclear launch sequence that will destroy the entire world.
Our sources have told us that the nuclear launch sequence is run from a shell script, and have also given us a tree showing the contents of the Doctor's computer (the flash drive has been added to show where in the structure it will appear):
NO_NUCLEAR_LAUNCH_SEQUENCES_HERE/
nopeNotALaunchSequence.sh
TOP_SECRET/
SERIOUSLY_TOP_SECRET/
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <!DOCTYPE html> | |
| <html><head><link rel="stylesheet" id="theme" href="chrome-extension://febilkbfcbhebfnokafefeacimjdckgl/theme/Clearness.css"></head><body><h1 id="w01d05-quiz-clearing-things-up">W01D05 Quiz, Clearing things up</h1> | |
| <h2 id="implicit-returns-vs-side-effects">Implicit returns vs side effects</h2> | |
| <p>An implicit returned is what is returned by a method that <strong>does not</strong> have a <code>return</code> statement. Remember: <strong>everything</strong> in Ruby returns <em>something</em>, and a method will return the <strong>last thing</strong> that was retured <em>inside</em> the method, <em>unless</em> the method has a <code>return</code> statement.</p> | |
| <p>A side effect is something that takes place <strong>outside</strong> of a method as a result of that method being executed, but is <strong>not</strong> explicitly returned by the method, nor necessarily implicitly returned.</p> | |
| <h4 id="for-example-">For example:</h4> | |
| <pre><code><span class="function"><span class="keyword">def</span> <span |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Hello!</title> | |
| </head> | |
| <body> | |
| <h1>What an elegant webpage.</h1> | |
| </body> | |
| </html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <!DOCTYPE html> |
Meets expectations
Your d3code.js file seems to contain entirely HTML. Why is it named .js?
I'm not a stickler for following convention with file structure, since I'm all for people organizing their files in a way that makes sense to themselves. However, I have difficulty seeing the logic behind this structure. For instance: you have .html files in two completely separate folders. What was the rationale for organizing files as you did?
There are lots of "app_SOMETHING" files floating around. I'm unsure whether these are actually used in the app... Are they just data backups? If so, I would have liked to have seen them partitioned off in a "backups" folder.
Virtually all of the front-end Javascript is in one file that's over 700 lines long. During our meetings I could see group members physically struggling to scroll through and find stuff in the file. This is really the whole reason for splitting code into separate files in the first place: to keep from having to scroll and find so much.
- Your API includes at least 2 models, one of which may be a user
- Your models include at least one association
- Your API has RESTful routes as appropriate
I'm intrigued by how you required your env.js and how you connected to your database. Nothing wrong with either of them, except perhaps that it adds some extra length to your app.js; just never seen it done that way before.
OlderNewer