Skip to main content

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

Popular posts from this blog

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone https://github.com/tfnico/config-mr.git mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git
    -> ~/.atom/*

config-mr.git
    -> ~/.mrconfig
    -> ~/.config/mr/*

config-tmuxinator.git  
    -> ~/.tmuxinator/*

config-vim.git
    -> ~/.vimrc
    -> ~/.vim/*

config-bin.git   
    -> ~/bin/*

config-git.git          
    -> ~/.gitconfig

config-tmux.git  
    -> ~/.tmux.conf    

config-zsh.git
    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…