Fork me on GitHub

home

Digging up the past

July 17, 2013 | Photography | No comments

In a good way.

I’ve been wanting a slide duplicator for some time now. I’ve got a lot of slides from college as well as a lot of family slides that I want to digitize. I picked up a Pentax Bellows M with Slide Duplicator off of eBay for a damn good price.

Below is a quick test with minor adjustments. I attached an old Pentax K mount Sigma 70-200 on there and adjusted it in to place. And voila. Mom, Dad, my Sister & Iggy the dog. The date says December 1973 but I think that’s probably the processing date and that the photo is from earlier in the year.

Mom, Dad, Sister & Iggy

The original wasn’t the sharpest photo in the world, but looking at how sharp the dust specks are I think this setup will do just fine ;)

I would have much preferred to use one of my 50mm Pentax lenses but I needed to pull back to get the right magnification adjustment for the APC sensor in the camera. Maybe now I need to find myself a nice 85mm lens to use here? Just don’t tell the wife I said that ;)

I’ve never been able to justify a dedicated slide scanner. But for $80 shipped I couldn’t pass this up. So now I need to dig up a bunch of slides and get my parents to mail me what they have all boxed up and get to work.

Its a lot to do but I’m quite looking forward to it…

So, who likes that new Y! nav bar on Flickr?

July 13, 2013 | Computers | No comments

Yeah, that’s what I thought. There’s a lot going on in the Flickr interface as it is. Adding a garish purple Yahoo! bar across the top just sends my eyes in to fits.

So here’s a bit of CSS that’ll hide nav bar in its current incarnation:

  1.  body.with-eyebrow #eyebrow {
  2.   display: none;
  3.  }
  4.  body.with-eyebrow {
  5.   background-position: left top !important;
  6.  }
  7.  body.with-eyebrow #global-nav {
  8.   top: 0 !important;
  9.  }
  10.  body.with-eyebrow .subnav-refresh {
  11.   margin-top: 0 !important;
  12.  }

Now, here’s the tricky part: where do you put this? Most browsers include a user stylesheet override that can be edited. Its just a matter of where this file is.

For example, on OSX using Chromium that file is located at ~/Library/Application\ Support/Chromium/Default/User\ StyleSheets/Custom.css

Finding the location of the file on your specific browser is outside the scope of this article. So do a quick search on Google, edit your custom CSS file, and bask in the glory of a less suckage on the flickr interface.

Point Reyes

July 7, 2013 | Photography, Travel | No comments

I think that I’ve found my favorite isolated place in California.

Rolling Waves at South Beach, Point Reyes

We’ve made a couple of trips out there lately and despite it almost always being foggy and cold its a wonderfully serene place. Most folks seem to head out to the lighthouse and then leave without exploring the beaches and cliffs. This means that we can spend a nice and quiet time on the beach wandering, talking, reading, or photographing.

This isn’t to say that the area around the lighthouse isn’t worth exploring. It is (the shack and deer photos below are from that area).

(more…)

A few handy git aliases

May 16, 2013 | *nix, Computers | 1 comment

I finally got fed up with some repetitive Git tasks and decided to make a few aliases in my .gitconfig file. Here are the commands, they all assume that they’re run from a valid git repo:

Push your current branch to your upstream repository

How often do you repeat the git command to push your current branch by typing git push origin [current-branch-name] because you never remember to set up the branch to track? Does this sound easier?

  1.  $ git pb

Alternately, here, you can add a default push method to your .gitconfig:

  1.  [push]
  2.   default = current

So that you can just call git push to and have git automatically assume you typed git push origin [branch-name]

Pull just the current branches updates

With larger groups of developers it is easy for a git pull to fetch a lot of new refs that you don’t care about. This alias shortcuts git pull origin [current-branch-name].

  1.  $ git up

A quick and easy update of just what you care about. Save big the git pull for lunch time or a coffee break.

Open the current branch on GitHub

We use GitHub Enterprise at work and going to look at the current branch/repo on the server is pretty common. So to make it super quick to get where you want to go this command will open up the GitHub server to the current repo and branch that you’re on. This works with self-hosted GitHub FI/Enterprise installs as well as public GitHub.

  1.  $ git gh

Open up GitHub to a new Pull Request

As a part of using GitHub Enterprise at work we’ve heavily adopted Pull Requests as the primary method of requesting code reviews and for pulling approved code in to master. However constantly finding the branch or manipulating browser history becomes tiresome. So this alias opens up GitHub to ‘/owner/repoName/pulls/new/current-branch-name‘ so that you can fill in a detailed pull request (you are filling out a pull request with a description and testing plan, right?).

  1.  $ git pr

Git log graph on the Cli

I don’t now about you, but I’ve not been able to get on board with the dedicated git apps for browsing and visualizing history trees, but once in a while I do want to look at the tree but don’t want to load an app to do it when a simple view on the cli will do.

  1.  $ git lg

Ok, enough jabber, gimme the code

Ok, its pretty straight forward. Just add this to your .gitconfig:

  1.  [alias]
  2.   lg = log --graph --pretty=format:'%Cred%h%Creset %C(yellow)%an%d%Creset %s %Cgreen(%cr)%Creset' --date=relative
  3.   pb = "!git push origin \"$(git rev-parse --abbrev-ref HEAD)\""
  4.   up = "!git pull origin \"$(git rev-parse --abbrev-ref HEAD)\""
  5.   pr = "!open \"$(git remote -v | grep origin | grep push | cut -f 2 | cut -d \" \" -f 1 | sed -e \"s|git@\\(.*\\):\\(.*\\).git|https://\\1/\\2|\")/pull/new/$(git rev-parse --abbrev-ref HEAD)\""
  6.   gh = "!open \"$(git remote -v | grep origin | grep push | cut -f 2 | cut -d \" \" -f 1 | sed -e \"s|git@\\(.*\\):\\(.*\\).git|https://\\1/\\2|\")/tree/$(git rev-parse --abbrev-ref HEAD)\""

Are those ugly? Sure. Do they help? Yep!

I’m sure as time goes on I’ll figure out a few more. Or maybe the three of you that actually read this far have suggestions? Lemme know.