Things to do in Ann Arbor

An out-of-town friend asked for suggestions about things to do during a visit to Ann Arbor. Here are my suggestions to him:

• The University of Michigan Art Museum is very nice: http://www.umma.umich.edu/
• Ann Arbor has an iconic, world-class deli, Zingermans: http://www.zingermansdeli.com
• If it's a nice day, you might enjoy a walk in the Matthaei Botanical Gardens & Nichols Arboretum: http://mbgna.umich.edu
• The downtown area, especially Main Street, has a many nice shops and restaurants.
• If you want a fairly upscale dinner, the Earle is very good. http://theearle.com/ And they have some nice specials during happy hour 5-8 weekdays.
• Kerrytown is a nice indoor collection of shops and a market: http://www.kerrytown.com/ There's a nice farmer's market there too Saturdays and Wednesdays from 7am-3pm.
• If you're looking to see a show, you could check the Ark http://www.theark.org/ , the Kerrytown Concert House http://www.kerrytownconcerthouse.com/ or Performance Network http://www.performancenetwork.org/

Preview of my "Refactor Your Software Career" talk

On Oct 24, 2012, I will be presenting a talk, "Refactor Your Software Career" to the Agile Groupies meeting in Ann Arbor at the Forge. I'll be sharing my journey from stagnant software developer to my current position at Pillar as a software craftsman and agile consultant, along with specific actions I took to get there, and strategies that anyone can apply to improve their career path. I'll also touch on barriers to taking this kind of action and what helps to get past those barriers.

But a key component to my talk will be what I'm calling "Transformative Networking". My idea is that you can simultaneously improve your marketability (raise your skills and experience) and increase the number of people who might want to hire you even while you continue to work at a job that doesn't offer growth or networking.

Transformative Networking involves engaging in activities that share as many of the following attributes as possible:

• creating real value (like volunteering or teaching)
• in your desired field (volunteering is good, volunteer coding is better)
• with others (solo coding a website for a charity isn't as good as being on a team doing it)
• in person (there's no better way to present yourself than by working with someone in person)
• with people in your target companies (if you want to work at a company, let their employees get to know you)

If you engage in activities like this (and my talk will include specific examples of ones I participated in), you can not help but increase your skill sets and get noticed.
 

UPDATE: The Forge Open House Date Moved

As I mentioned in a previous post, Pillar is holding an open house at our new facility in Ann Arbor called the Forge.

There is a new date for the open house: June 21, 6-9pm. If you already registered for the May date, you will receive updated information by email.

Please see my previous post for full details, or click here to register. (It may take a few days for the date change to appear on the registration site.)

Jenkins and Subversion and "Send separate e-mails to individuals who broke the build"

My current team wanted to use Jenkins' "Send separate e-mails to individuals who broke the build" feature. We use Subversion, and our Subversion usernames are not email addresses. And because my team members belong to different companies, we can't specify "Default user e-mail suffix" even if our Subversion usernames were the names of our email accounts.

For a while, I couldn't figure out how configure Jenkins to do what I want. I did a little googling and found out that Jenkins has a "People" page (for example, Apache's^* People page is: https://builds.apache.org/people/ ). Clicking on a person's User Id link takes you to their page. With our Jenkins configuration, a user's page has a "Configure" link on the right. Clicking that allows them to enter their name and a variety of other details, including Email address! That should allow me to use "Send separate e-mails to individuals who broke the build" the way my team asked.


* If you want to look at a big, vibrant Jenkins installation, check out the public Apache Jenkins machine: https://builds.apache.org/ Obviously it is read-only, but it has lots of projects, so there is usually something building, and you can see lots of examples of different statuses.

Jenkins Violations plugin quirk

Now that I got OpenCover working with Jenkins, I decided to go after fxCop. Here's the command-line I settled on:

"C:\Program Files (x86)\Microsoft Fxcop 10.0\fxcopcmd.exe" /oxsl:none /igc /f:OurApp.AssemblyToCover1.dll  /f:OurApp.AssemblyToCover2.dll /out:fxcop_results.xml /d:"c:\Program Files (x86)\Microsoft ASP.NET\ASP.NET MVC 3\Assemblies"

The /oxsl: argument specifies no xsl transformation on the output (I'm using the Violations plugin which reads the native xml).

The /d: argument points to where System.Web.Mvc.dll lives, which one of our assemblies depends on.

As I mentioned before, I want to exclude several assemblies from analysis, so I specified the ones I want included by using /f: arguments (one per assembly).

NOTE: Getting the Violations plugin to work was easy once I realized one thing: the "XML filename pattern" must either be a filename pattern only (in which case the file will be in the Jenkins build project's workspace directory) or it must be in a directory below the Jenkins build project's workspace directory (for example results\fxCop*.xml) Absolute paths and relative paths starting with "..\" do not work.

I Got OpenCover to Work with Jenkins

As I mentioned before, a team that I am coaching is using Jenkins for CI. We wanted to automate code coverage measurements for the .Net code in specific assemblies of our solution. (Others are third-party or machine generated, so we don't have unit tests for them.) It took me longer than I would have liked, but I did get OpenCover running and generating reports as part of our Jenkins build.

One hurdle was that Jenkins seems to need to be run as user with administrator rights in order for OpenCover to work. So I created one and assigned it in the "Log On" tab.

In my Jenkins job, I opened "Add build step" and selected "Execute Windows batch command". In there, I gave the command line:

"C:\Program Files (x86)\OpenCover\OpenCover.Console.exe" -target:"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe" -targetargs:"/testcontainer:E:\Jenkins\jobs\BuildOurApp\workspace\TRUNK\OurApp.UnitTests\bin\release\OurApp.UnitTests.dll" -filter:"+[OurApp.AssemblyToCover1]* +[OurApp.AssemblyToCover2]*" -register:user -mergebyhash -output:E:\Jenkins\jobs\BuildOurApp\workspace\FilteredCodeCoverage.xml

As an aside, I often have Jenkins jobs with several batch command sections. I found it annoying to scroll up and down and quickly find the one I was looking to edit. So I've started marking the top of each script:

REM   _      ___  _  __ _____  
REM  | |    |_ _|| |/ /| ____| 
REM  | |     | | | ' / |  _|   
REM  | |___  | | | . \ | |___  
REM  |_____||___||_|\_\|_____| 
REM                            
REM   _____  _   _  ___  ____  
REM  |_   _|| | | ||_ _|/ ___| 
REM    | |  | |_| | | | \___ \ 
REM    | |  |  _  | | |  ___) |
REM    |_|  |_| |_||___||____/ 

 
( http://patorjk.com/software/taag/ , "Standard" font, unchecked "Smush Letters Together" )


I have the HTML Publisher plugin installed, so I enabled it, clicked Add to add a row and specified:

E:\Jenkins\jobs\BuildOurApp\FilteredCodeCoverageReport 

index.htm

Code Coverage Report

as the arguments and it's all set! Now coverage is computed automatically and my team has a single URL for a summary report with drill-down details.

Coding in the Clink - Another Success!

Today I again had the privilege of attending a Coding in the Clink , this time number 6. This was my third visit to Marion Correctional Institute. (Read about my first visit and my second visit.) The last time I went was June 2011. Since then, the Java Guys have definitely continued to improve, in TDD, pairing, and Java. And as before, the guys were curious, hard working, and fun to be around.

As always, Dan Wiebe did a great facilitation job, and this time added new twists. He had us break from CodeRetreat tradition in a couple of significant ways (besides the fact that prison lunch never qualifies as "something good, catered"): 

• No GoL, instead Mancala  (We were all surprised at what a challenging problem Mancala is, given the fairly simple rules. I think it's more interesting than GoL.)
• Instead of deleting our code after each round, we left it there for the next pair. And he asked us to not pair with the same person twice, and not work on the same code twice

In round 2, when I sat down at someone else's code for the first time, it took most of that round just for me and my pair to make sense out of what was there. (Most pairs experienced this too.) I found that each subsequent code base I visited was easier to understand (and most other devs found this too). It was cool to sit down to each subsequent code base and find something better than I had previously sat down to.

For our final round, everyone agreed to go back to the workstation where we started. I'm not sure there was any consensus around that experience. For me, I was sad to find there weren't many more tests 5 hours later than when my pair and I first left it. (Which seems odd, given the experience of improving codebases we had up until the last round. Maybe I was having some bias when looking at "what they did to my code"?)

I'll close with the logo for today's event, as created by one of the inmates, Mark Roberts: