- create new project
- choose "scrum software development"
- click 'select' on the next screen to use the default issue type for now
- choose a name and project lead
- go to 'project administration' (this option is in different places depending on your view)
- you should be viewing the summary now. do these:
- issue types
# spec_helper.rb | |
RSpec.configure do |config| | |
# earlier configurations omitted ... | |
# Set config.use_transactional_fixtures to false | |
config.use_transactional_fixtures = false | |
config.before(:suite) do | |
DatabaseCleaner.strategy = :truncation |
class AnyController < ApplicationController | |
# HTTP authentication should be used for staging to prevent unauthorized outside access to application. | |
before_filter :authenticate if Rails.env.staging? | |
private | |
def authenticate | |
authenticate_or_request_with_http_basic do |user,pass| | |
user == "usernamehere" && pass == "passwordhere" |
// Use Gists to store code you would like to remember later on | |
console.log(window); // log the "window" object to the console |
Comments: "stefankendall.com: 10 questions to ask your potential employer" | |
URL: http://www.stefankendall.com/2013/11/10-questions-to-ask-your-potential.html | |
The interview is all too often driven by the employer. Can you handle this workload? What are your strengths and weaknesses? How do you feel about this aspect of the business? | |
But at the end of the interview, you do not know enough to know if you will actually love and enjoy the work. How many developers or designers do you know who have worked at a place for less than a year? Less than 9 months? I bet more than a few. | |
Here's some questions you should ask before committing a significant portion of your life to a company. |
jar is an object in front of you. It is tall and from above looks like a circle.
a jar has stuff in it. there can be either peanut butter, which is brown in color, or jelly, which is purple in color. peanut butter jar and jelly jar. a jar has three parts - the inner stuff is one, and the outer stuff is in two pieces: the top and the bottom. you can see the division between the two parts. the bottom is the part that is facing down, the top is facing up.
bag of bread is an object in front of you. it has two parts - an outer container and an inner material. the bag is the container and what is inside in the bread. there are many nearly-identical items that are all bread. they are individually called slices. a slice of bread is an individual item.
knife is another object in front of you. it is the only remaining object. it is silver in color and has the shape of a wide line. there are two ends to it handle and blade. the handle is the thicker end. the blade
# CS function | |
function cs () { | |
cd $1; ls "-lahG" | |
} |
essentially like cloning on github's servers - but that's inconsequential, mostly.. also: forks are not automatically up to date (relative to repo you forked)! your fork creates a snapshot of the original repo at the time you fork it.
-
fork on github
-
creates a clone on github servers
-
copy url of that clone
-
git clone [url]
- clones the content of your fork to your local machine
curl -u 'USER' https://api.github.com/user/repos -d '{"name":"REPO"}'
Replace USER
with your username and REPO
with the intended repo name. Include all quotes above.
The do the usual:
git remote add origin git@github.com:USER/REPO.git
git push origin master
I hereby claim:
- I am vcavallo on github.
- I am vcavallo (https://keybase.io/vcavallo) on keybase.
- I have a public key ASAA6bamIo8LhRq8sehFLen9QC5WqQNkIWZQ9cx9rk5t0go
To claim this, I am signing this object: