hyperbola :: lifestream
Post image

The converters are central to #artichoke. Changing this core abstraction was painful: 84 files changed, 2000 lines added, 2800 lines removed. #fail #git

permalink

Extracting cactusref required completely rewriting #git history, updating docs, adding a build, adding benches, importing my blog post, updating links in the blog post #artichoke

permalink
Post image

#git bisect is why it's important that your repo be buildable at every commit. Currently fixing a massive memory leak in ferrocarril #fail

permalink

Adding #ci to a project is encouraging such better code hygiene. Because I want to make sure the build stays green, I actually make PRs even if it is only me approving them. Seeing the code in the browser makes it easier to review than #git diff #win

permalink

this is just one example of the times #git has saved my life #win

permalink

Recently restructured my #dotfiles and added a Makefile so they don't live in $HOME (git clean terrifies me) #git

permalink

Woo! First 2 hyperbola releases with #git tags today #win. Also local development. dev + ops = #devops

permalink

Next #devops steps for hyperbola: Rebuild machine from scratch on 64-bit kernel; use #docker and dockerize all services: nginx, staging django, prod django, MySQL; real deploy step; #git tag releases

permalink

I have no idea why, but since I've been working at #box, I don't #git pull. I always fetch and merge --ff-only or rebase. Only time I ever use pull is via pull --rebase if I get ff-rejected on push

permalink

Just forked, edited code, submitted a pull request, and got it merged all from the browser #win #git #github

permalink

I had a cronjob launching every minute that updated remotes on about 40 #git repos. I've apparently had ~50 git processes running all the time for about a year now. #fail

permalink
Post image

#versioncontrol, or the lack thereof. This was my first major software project. I was a junior in high school. I was making a symbolic math thing. #fail or the reasons any CS class should teach #git

permalink

My wiki was spammed and turned into a link farm for discount pharmaceuticals. Good thing its backed by #git -- fixing it was trivial

permalink

Something something something #git ... something something something complete

permalink

I don't understand why people think they need build scripts for their dotfiles. #fail Just keep your $HOME in #git: git init && git remote add ...

permalink

why `svn status` prints nothing when you have a clean working directory is beyond me. #git ftw

permalink
Post image

rebased some already pushed commits to clean up my history and forced the push. I feel so dirty. #git #fail

permalink