Skip to content
View efischer19's full-sized avatar

Block or report efischer19

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. personal_vim personal_vim Public

    My Personal Vim configuration, made to travel.

    Vim Script 1

  2. golang_ctci golang_ctci Public

    Working my way through cracking the coding interview in Go, because I want to learn it

    Go 88 5

  3. ft-frontend ft-frontend Public

    Frontend code for the family photo sharing blog I'm building

    JavaScript

  4. whassat whassat Public

    Multilingual object detection in <6MB of neatly encapsulated javascript

    JavaScript

  5. fhoopz fhoopz Public

    Simple fantasy hoops in slack

    Python

  6. Commit Hygiene; a treatise on the Wh... Commit Hygiene; a treatise on the Whys and Hows
    1
    ## Introduction
    2
    
                  
    3
    Commits (or changesets/patches) are the effective results of a developer's coding efforts. They describe a delta, or difference in contents that all other developers using a given codebase should also apply to their copies of the codebase, keeping it moving forward towards a common goal.
    4
    
                  
    5
    It would seem apparent that there exist "better" and "worse" ways of creating, describing, and otherwise talking about these individual changes, but actually nailing down a consensus definition of "good" or "best" is often tricky. What follows here is one experienced developer's opinion of why it matters and what "good" means, along with some links to back that up.