My résumé in git log

I was helping a friend shape up his CV/résumé recently. Along the way I thought it would be cool to maybe have a bit more original format than the traditional paper, so I tried it out on mine just for fun:

$ git log career

commit 6f554814186594113ce2060aed3e4240b7fb852e
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Mon Jul 01 11:01:59 2011 +0200

Software developer at Viaboxx Systems

commit 1478c77d52fe41ba855fa2181527a7deea480e58
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Tue Jan 3 10:03:18 2009 +0200

Senior software developer at IP Labs GmbH/FujiFilm Group
- Introduced a range of agile practices, like weekly iterations,
standup-meetings and continuous integration and deployment.
- Lead the first Scrum project, integrating services with FujiFilm
partners across the Atlantic and in Asia.

commit 23265936762d4ccaab8c8c0e4ff088650b4a63e2
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Tue Oct 16 10:02:44 2006 +0200

Consultant at Objectware

Various projects doing on-site training, coaching and development.
Further details and recommendations are available on request.

commit 3af763c404f42fd5deadb266db60f939d6740dbd
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Fri Jan 5 23:46:57 2005 +0200

System developer at Primetime AS

Web application developer. Maintained and improved a Content
Management System, as well as implementing a new one based on open
source software.

commit 00049ded811df3371e143de478a309883a33de6d
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Fri Sep 21 12:18:57 2004 +0200

Consultant at University of Oslo

Prototype project for the IT-tool managing the Quality Assurance Program.
Implemented as a J2EE web-application based on the Apache Struts framework.

$ git log education

commit fc14673f063ec6217c012272ae27d4c1d3e8659e
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Tue Aug 14 14:20:44 2003 +0200

University of Oslo (3 years)

Graduated as MSc, Informatics. Title of master thesis: The Use of
Open-Source and Open Standards in Web Content Management Systems.

commit d646e2774b773c07680aebac651fe05cad54e481
Author: Thomas Ferris Nicolaisen <tfnico@***.com>
Date: Tue Aug 14 14:18:40 2001 +0200

Agder University College (2 years)

Studied computer engineering; physics, mathematics, network and
programming.

Not the most readable or printer friendly, but kinda cool.

Next step is to put it in a real git repository. Nice way to filter out non-serious headhunters :)

Comments

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...

Git-SVN Mirror without the annoying update-ref

This post is part of a series on Git and Subversion . To see all the related posts, screencasts and other resources, please click here . So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our fetching repo. Set up a bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using git log --graph --...