17

If my GitHub contributions graph was any more pathetically anemic, it would be my dating history.

Comments
  • 2
    You stud! If this was my dating history it'd be my 2nd best year~
  • 3
    Can I post my dating history too?
  • 1
    How are you guys' commit frequencies so low? Please tell me you use another platform or have backups of your code.
  • 5
    @neeno if I go see my commit history without logging in, it would look pretty much like that, too - but only because most of my commits are to private (company) repos, which don't show on pub commit history.

    But yeah, if those are your actual commit histories... What? How?
  • 0
  • 1
    @neeno I guess I'm not doing very interesting projects...I tend to commit a lot of one-off proof-of-concept repos. Small-scale stuff just for honks & giggles.
  • 1
    @cafecortado OUCH. There are apps for that.... :)
  • 0
    @100110111 I tend to work solo and crank-out my code locally and then only commit the finished, bug-free repo once finished. Usually no more than 1 or 2 commits with only ever a single branch. I'm not saying I'm actually good at this stuff, just tidy.
  • 2
    This post physically hurt.
  • 1
    @LotsOfCaffeine Just try to imagine what it's done for my self-confidence.
  • 4
    @neeno Not everyone does GitHub / open source work. Most company repos are on other platforms anyway, so for a professional dev this wouldn't be unusual.
  • 2
    @AlmondSauce reals. All the code I write these days isn't publicly available in any capacity so my personal GitHub looks like I died lol.
  • 2
    *Trivia*
    Guess when I employed by this picture!
    (Hint: most of my corporate code isn't on GitHub)
  • 0
    @vintprox Looks like you took a holiday break.
  • 5
    I quit my job at some point in this graph
  • 0
    I guess it's fair to note that my own repos didn't blow up like most people because most of the interests gets generated from my Medium posts that I use to explain the concepts.
  • 1
    @neeno we commit alright, just not publicly.
  • 1
    @jasonsalas Jesus Christ. I had a coworker do what you're currently doing. When he left the company he left me six months worth of uncommitted code to merge from his local repo, it took me a month to work through his commits and figure out what was deprecated and updated. At least push your code to a branch called dev or something and merge every so often to a merging branch so you don't have to bust your ass every time you push your code.
  • 2
    @100110111 @null-pointer-ex oh I didn't know it only showed commits to private repos if you were logged in. In that case mine probably looks empty too, I mostly do stuff in private repos.

    @jasonsalas makes sense. I prefer to write a very small prototype, create a repo for it and make lots of small commits.

    @AlmondSauce yeah agreed, I figured people with emptier commit histories might just not use gh.
  • 0
    @vomitmachine Nah, I always keep a nicely-organized branch tree. I set it up intuitively and clean-up afterward. No hunting necessary.
Add Comment