<div>
<h1 role="heading">Main Title</h1>
<form action="/" method="get" role="search">
<label for="search-field">Search:</label>
<input type="search" role="searchbox">
<input type="submit" role="button">
</form>
</div>
<nav role="navigation">
In the context of Node, what is a module?
- A module in Node seems similar to Ruby in that it simplifies and organizes code, it can be plugged in and used in different places, but it is like a class because it stands alone. Like a cute little code nugget.
The code examples from the second blog post look very different from the first. Why?
- From what I understand, it's because require.js is simplifying things and doing work for you, whereas in the first example, you need to be more explicit.
Guiding Questions to Define The Relationship: • What are your learning goals for this project?
all: spend qt together <3 Ali => learn js Claudia => learn js, have fun, learn to unit test js Kris => same
• What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
-
What is something you learned that was particularly surprising/interesting?
It was interesting to learn that $() is shorthand for calling jQuery.
I also enjoyed seeing how JS and jQuery work together by selecting things and setting them to a variable. The .filter and .not functions are new and interesting
Sandi Metz's Rules for Developers
Which of Sandi's rules do you feel like might be the hardest to follow—why?
Never having written an app in JS, I have a limited perspective, but the rules do seem overly ridgid. I have a hard time believing that every app could be constructed in exactly this way. But It does seem a good idea to have a structure to shoot for. I think the hardest one to implement, for me at least, would be only one instance variable in a view. Depending on the view, there are a lot of things that may need to get passed in. But the author uses partials and other work arounds. I would be intersted to see how the rules play out in an actual application. Writing code for a rails app may be very different.
What does it mean to concatenate files? Find an image of an example concatenated file. Why would we want to concatenate files?
- To join together files for fast loading applications.
#How to write an individual commit message:
Keep it concise and consistent.
##The Seven Rules of a Great Git Commit Message:
- Separate subject from body with a blank line: Though not required, it's a good idea to begin the commit message with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. The text up to the first blank line in a commit message is treated as the commit title, and that title is used throughout Git. For example, git-format-patch(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body. When a commit merits a bit of explanation and context, you need to write a body
## Models, Databases, Relationships in Rails | |
#### What is the difference between a primary key and a foreign key? Where would we find a primary key? | |
What would it be called by default? Where would we find a foreign key? What is the naming convention for a foreign key? | |
Primary key is the id in the table you're working in, the foreign key is the connected key from another table you're | |
joining or referencing in the current table. The primary key is generated when the table is created. Primary cannot be | |
repeated in the table. Foreign key is a relationship that is formed, primary key of another table. Name of table_id is | |
convention for the foreign key. | |
#### Write down one example of: |