thePaulista

System development/Usability/Related Theories
First thing to do: 1. assess 2. identify functions 3. estimate
Buy or build?
  now buying a vendor system is generally considered a cheaper option due to substantial development & maintenance cost and increased functionality of the vendor solutions

Software Development LIfe Cycle (SDLC)
planning and analysis
  requirement analysis
    "as-is" vs. "to be" processes
    USE CASES: intense documentation. includes workflows (normal flow, alternative flow), before and after system stastus of a user action, use

thePaulista

for app in $(heroku apps); do heroku apps:destroy --app $app --confirm $app; done

thePaulista

rails new rails_engine -d postgresql --skip-test-unit --skip-turbolinks --skip-spring
___________________________________________________________________________
source 'https://rubygems.org'

gem 'rails', '4.1.4'
gem 'sqlite3'
gem 'sass-rails', '~> 4.0.3'
gem 'uglifier', '>= 1.3.0'
gem 'coffee-rails', '~> 4.0.0'
gem 'jquery-rails'

thePaulista

-----------------------------
test_helper.rb for MINITEST
---------------------------------
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../../config/environment', __FILE__)
require 'rails/test_help'
require 'minitest/pride'
require 'webmock' #fakes http request
require 'vcr'

thePaulista

rails g rspec:install
______________________________________________________________________


bundle exec figaro install

http://stackoverflow.com/questions/21884085/where-do-i-place-stripes-publishable-and-secret-keys

Rails.configuration.stripe = {
  :publishable_key => ENV['PUBLISHABLE_KEY'],

thePaulista

" ========================================================================
"                             Vundle stuff
" ========================================================================
set nocompatible " Required by vundle
filetype off     " Required by vundle

" set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()

thePaulista

your strengths:
JON:  he's a good punching bag, freestyling code
Kris: styling
Hedy: good at punching Jon. not sure, good at finding resources and implementing (?)
Jared: 

weaknesses:
JON: testing
KRIS: confidence
HEDY: everything! confidence!

thePaulista

Cheat Sheet:
   http://vim.rtorr.com/   (START with this one)
   http://www.catswhocode.com/blog/130-essential-vim-commands

Vim Adventure: vim game to help you with navigation. 
   http://vim-adventures.com/

Vim Golf: check your keystroke count.  It's the exercism of vim. 
   http://www.vimgolf.com/

thePaulista

" ========================================================================
" Vundle stuff
" ========================================================================
set nocompatible " Required by vundle
filetype off     " Required by vundle

" set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()

thePaulista

Availability: Jon - 100%, flexible with hours,
              Chris -  mostly open, 
              Hedy - 100% flexible

Strengths:  Jon - good at solving problems, 
            Chris - solid in Ruby, good at testing,
            Hedy - diagraming ideas, ruby
            
Weakness: Jon - testing (want to jump right into the coding for solutions);