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]

Comments

  1. This is a good point. Many developers assume that the state of the infrastructure is unchangeable.

    At my previous site, I discovered that forum.java.sun.com was blocked by the firewall. Initially, I got pretty angry and resigned. Then I sent an email to the firewall administrator. The response I got was illuminating:

    * The blocking was part of a preinstalled filter blocking forum.*
    * The firewall administrator opened access right away.
    * The firewall administrator got happy that he got direct feedback, and not the usual grumbling in the hallways.
    * He also remarked that people almost never request filter changes.

    Sometimes, a fight isn't necessary. Problems that you think may be due to difficult people, like the network admin, might just be the way they are because nobody pointed them out.

    BTW: Thomas: You're more than welcome on Monday if you wanna make the trip!

    ReplyDelete
  2. I'd love to come, Johannes, but it's a bit too much travel-hassle-money for me, I'm afraid :)

    Thanks for your comment! Good story.

    ReplyDelete

Post a Comment

Popular posts from this blog

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

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

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

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 --