This is a good description of working with merging or rebasing in git. What they do and how to deal with them

Merging vs Rebasing (from Atlasian)

Use git log:

git log -S <String to search for> --author <author to restrict by, usually it's you> --since <how long since you made the change>

If git complains with this error:

fatal: bad object refs/remotes/origin/HEAD
error: failed to run repack

This may happen if upstream branches have been removed and your origin is pointing to it. You can confirm this by running:

An article on meta-programming in ruby. Source to use as inspiration for screenplay pattern in ruby

Build your own RSpec - introduction to DSL and metaprogramming

Usually a cucumber step definition will have some sort of regular expression capture:

Given(/^I have (\d+) dollars in my account$/) do |amount|
  #step logic
end

As the Given is specified above the amount argument will still be a st...

Rationale: Working in a git feature branch is convenient, the Trello board acts as a simple todo list specific to that work. Useful for sharing thoughts with other people also working on the branch

Version control (ie. git) your home directory. The post below describes a process (and has further links to examples) of a way that moves the whole version control aspect away:

https://developer.atlassian.com/blog/2016/02/best-way-to-store-dotfil...

Article on rails about not using @vsrisbles in controllers. Really nice approach

This retrospective was run as part of an employee on boarding experience. It was a small group (3 participants).

Goal: Where are we, what does success look like? (Futurespective)
Time: 1 hr

Structure

• Weather Report (set the stage)
• ...

The directories scanned for steps are determined by the feature file(s)/directories passed to the cucumber command. Cucumber will look in the sub-directories of the feature files

features
  billing
    credit_card.feature
  scoring
    multi_...