Skip to main content

Fight For Your Infrastructure

The 97 Things Every Programmer Should Know book was recently released. Kevlin Henney has gathered together advice from a wide bunch of programmers, many of which are from the Norwegian developer scene, and a good few of which I consider old friends.

They are even arranging a release party in Oslo next Monday at XP-meetup. So far, over 250 people have RSVP'ed to attend the event.

Unfortunately, I didn't get my act together to write a submission for the book before after the deadline, but I submitted it anyhow, in case of any 2nd edition of the book.

Anyhow, out of sheer jealously of all the attention the accepted submissions are receiving now, I figured I'd post mine here:

Fight For Your Infrastructure

It is in your role as a programmer to demand proper infrastructure from your organization, simply because nobody else will. If the organization does not provide it for you, you must explain them what you require, and dedicate as much of your own time as necessary until an adequate support level is reached. This is a continuous effort; As new hardware, tools and frameworks appear every year, you must consider which of these can be of benefit for your team, and make sure installations proceed smoothly. Be it the introduction of solid-state-drives for your team, or moving to a new distributed source code management tool, you must push for these changes to happen.

Some would argue that this is a job for IT-administrators, but unfortunately, this is often not the case. Some organizations suffer from having an underskilled or understaffed IT department, and even for experienced technicians, it is difficult to keep up with the portfolio of developer tools available. Some organizations are budget-wise structured in such a way that the IT department is not rewarded for investing in programming infrastructure, and provide programmers with the same hard- and software constraints as any other office worker.

The appropriate suite of tools depend on the size, location and configuration of the team. Starting with the most elementary pieces of infrastructure, a proper monitor setup and a powerful desktop computer is obligatory for almost any programmer, as well as mouse and keyboard of good quality. It is particularly good if the programmer can choose brand and models by personal preference.

Infrastructure is not only about IT. Basic environment requirements should include proper ventilation, and a kitchen-station nearby with free tea, coffee and water. To assist the flow of communication between programmers, there should be rooms freely available equipped with whiteboards, flip-charts and projectors.

Moving further into the infrastructure, programmers should have a solid network connection, allowing them to quickly access needed resources online. The internal network between developers and servers should be lightning fast, making it easy to do remote operations, like deployment and following logs.

Regarding services that should be provided internally, most would put a source code management tool on top of the list. Organizations are inreasingly discovering the use of continuous integration, and this environment should be powerful enough to provide feedback in the matter of minutes after a change in the source code. Knowledge bases such as wiki, issue tracker and pastebin should be standard in any developer environment.

On personal software, there should be room and routines for purchasing commercial licenses, as well as books and documentation. The operating system and application platform for which the programmers are developing should be flexible and practical, allowing scripted builds and automatic deployment, minimizing the amount of tedious repeated routines programmers have to go through.

Finally, there should be a presence of IT personnel that can absorb the infrastructure maintenance from the programmers. At the end of the day, it is our job to develop software, so outsourcing upgrades and monitoring to support staff should be allowed.

This work is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]

Popular posts from this blog

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…

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…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

The Best Log Viewer Ever

This is what it looks like when I want to have a look through the logfile, to see what a user did on one of our machines one day:


Read the whole story about how it works on the Viaboxx Systems blog (and upvote on DZone!).

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…