Skip to content

Instantly share code, notes, and snippets.

View lfinney's full-sized avatar

Luke Finney lfinney

23 followers · 14 following
View GitHub Profile
@lfinney
lfinney / LukeFinney_Prework.md
Created March 18, 2017 16:40

And so it begins...

@lfinney
lfinney / lfinney-post-grad-30-day-plan.md
Last active January 8, 2018 03:56
Post graduation 30-day plan for Luke Finney

Post-Grad Job Search Action Plan Template: Your first 30 Days

#1: 30-Day Job Search Action Plan

Create a schedule & goals for the first 30 days Post-Graduation

Daily Routine:

  • 7:00 - Alarm to wake up
  • 8:00 - Breakfast has been eaten, fresh cup of coffee in hand.
  • 8:00-8:45 - Work on code problems: Exercisms, Code Wars, etc.
  • 8:45-9:00 - Read coding-related news via reddit
  • 9:00-10:25 - Write and send Cold Outreach messages
@lfinney
lfinney / branches-prs-and-commits-oh-my.md
Last active May 31, 2021 18:13
Branches, PRs, and Commits. Oh, my!

Values (Things that are important)

  • A PR is a conversation about code, not just a means to an end to add code to a repository
  • A well written PR should be re viewable by a novice/junior programmer
  • A PR is best when it is short, has a clear focus, and contains a clear commit history
  • A developer should consider how a given commit will appear in a diff to those reviewing the code
  • A dev team should have a 'social contract' that defines how they are going to communicate and what things they are going to care about as a team.
  • A dev should strive to make other devs 'code switch' as little as possible by writing code that falls into an agreed upon standard deviation for the team.

Standards (General guidelines)

  • A feature branch merged into main, stage, or test environments should not negatively impact the applications ability to run correctly in any way