Skip to content

Instantly share code, notes, and snippets.

View pricees's full-sized avatar

Ted Price pricees

28 followers · 3 following
View GitHub Profile
@pricees
pricees / javascript_newbie_review.js
Last active February 24, 2016 15:49
Javascript newbie review
///////////////////////////////
///////////////////////////////
// "this"
///////////////////////////////
///////////////////////////////
// Global object
// - Node: reference via "global"
// - Browser: reference via "window"
//
@pricees
pricees / awesome_git_plugins.md
Last active February 19, 2016 16:22
Awesome Git Plugins

Fireplace (Clojure

  • cqp Opens quasi-repl (one liner)
  • cpp Evaluate innermost expression
  • cq% / cqc Prepopulate repl with codez
  • cpr Reload namespace, switch to repl

Commentary

  • gcc - comment section
@pricees
pricees / command-line-tools-for-mac.md
Created January 21, 2016 20:51
Command Line tools for the Mac

Command Line Tools for that Macintosh

15 Commands in 300 seconds

tee - Copy STDIN to STDOUT

@pricees
pricees / ruby_hook_methods.rb
Last active January 14, 2016 18:09
Ruby Hook Methods
#
# Go here for the runnable version: https://bit.run/s/5ts-In6lwLgFveVW```
#
# Out of the box Ruby hooks/callbacks
#
# Module#prepended
# Module#extended
# Module#included
# Module#method_added
# Module#method_removed
@pricees
pricees / ey_upgrade.md
Created January 12, 2016 17:08
Minimal downtime architecture upgrade with Engine Yard

Migration Path

  1. Create new prod environment on EngineYard
  • Latest OS tag on application server
  • Latest PG version on master, slave database
  • Latest Redis version
  1. Dump production slave https://goo.gl/dFz7T8 sudo -i eybackup -e mysql --new-backup k
@pricees
pricees / qa_bottleneck_experiments.md
Last active January 8, 2016 14:03
QA bottleneck experiments

Background

Issues:

  • We have limited QA human bandwidth.
  • Pull requests are bottlenecking in a "needs QA review" state.
  • QA is bogged down with manual/regression testing.
  • Communication and the hand-offs between the engineers, seit, and qa can be greatly improved.

Here is the outline of QA experiments/action-items we are going to try:

@pricees
pricees / the_ruby_object_model_or_method_lookup.md
Last active January 7, 2016 22:00
The Ruby Object Model or Method Lookup
@pricees
pricees / clt4tm.md
Last active December 15, 2015 20:00
Command Line Tools for that Macintosh

Command Line Tools for that Macintosh

15 Commands in 300 seconds

tee - Copy STDIN to STDOUT

@pricees
pricees / jr_developer_role_and_responsibilities.md
Last active August 29, 2015 14:27
Junior Developer Role and Responsibiltiies

Junior Developer

Role

Junior Developers are responsibile for honing and advancing their craft as software engineers. Their job is to pair with leads, architects and other team members. Junior Developers should trive to to gain as much exposure and understanding as possible to all layers of the stack, programming paradigms and practices. A junior developer should look to focus on a single layer, language and tool set of the stack. A junior developer should be able to identify components of the application and infrastructure in their domain. Junior Developers are expected to learn the proper lexicon and terminology for the domains they work in. Junior Developers are expected to ask questions until their understanding of a subject matter is clear for their purposes.

Responsibilities

Specific responsibilities of the Junior Developer include:

@pricees
pricees / developer_role_and_responsibiltiies.md
Last active August 29, 2015 14:27
Developer Role and Responsibilities.

Developer

Role

Developers are responsible for implementing software to achieve the business needs and goals of the project set forth by project stakeholders. Developers, with guidance from team leads, managers and architects, fill in the gaps between business requests and software implementation, including design, modeling, and analysis. Developers are expected to work in a dynamic and fast paced environment. Developers may code individually, in pairs, or collaborate with arbitrary members of a team.

Developers are expected to communicate clearly and efficiently with their manager and product stakeholder. Developers should be vigilant about obstacles that will impede reaching their development goals, both in quality and timeliness as agreed upon with the stakeholder. Developers are expected to communicate and revise expectations as obstacles come up; they are expected to raise any problem up through the management chain until these problem is given the attention it needs and/or is resolved.

R