Just a quick note…
In case you hadn’t heard the news CodePlex now supports Mercurial project hosting against a Mercurial client. The blog post on the CodePlex blog shows you how to connect to a project and the ins and outs of setting up new projects etc.
My last couple of posts have been about Mercurial. I keep discovering new things I like about it. Combining it with PowerShell also presents some exciting possibilities.
I have a couple of PowerShell scripts I’ve used for building stuff for a while. This one for instance.
$lastBuild = join-path $env:temp lastbuild.log
function b {
msbuild /l:"FileLogger,Microsoft.Build.Engine;logfile=$lastBuild" $args
}
function lb { notepad $lastBuild }
The advantage of this is that you can use the lb command to load the last build log into your favorite editor and browse or search it. The example above uses notepad but notepad2 is a better choice, especially if your log files are large. This beats scrolling up and down in the shell window looking for the root cause of build breaks etc.
So where does Mercurial come in? Turns out Mercurial’s repository cloning feature(s) mean you can create a “buddy build” to quickly test local commits before pushing them to the authoritative repository.
Mercurial ships as a command line tool. Here are some UI based tools to make it work that much better on Windows and in Visual Studio.
TortoiseHg – A Windows Explorer integration for Mercurial (You can download the latest versions of Mercurial and TortoiseHg from the Mercurial site)
HgScc – A source code control package for Visual Studio. This seems to be under pretty active development with versions for VS 2008 and VS 2010 Beta. It supports most of the features you’d expect from a SCC provider; project item state flagging and commit menu items etc.
TortoiseSVN’s TortoiseMerge – I sort of grew to like TortoiseMerge during my time using Subversion so I’m still using that as my diff’ing tool. You can configure both HgScc and TortoiseHg to use this for diff’ing.
I’ve been using Subversion to host my code on a Windows Home Server box for the past year or so. At about the same time distributed version control systems (DVCS) started to become the “hot new thing”. Git, Mercurial and Bazaar with their associated community hubs; GitHub, BitBucket and Launchpad are all getting a lot of traffic.
I’ve avoided moving a to distributed version control system because I’ve largely been very satisfied with Subversion for my single user, mostly connected scenario. The only place I’ve found Subversion lacking is in the completely disconnected case, which doesn’t happen to me very often. I’m also pretty conservative when it comes to version control, hot new features take second place to a reliable well documented “traditional” VCS like Subversion.
The result of all my F# hacking around over Christmas wasn’t just some notes on what not to do (my previous F# blog post). I actually got down to writing some more code for my n-body model in F#. I got down to reading some of “F# for Scientists” and a couple of really interesting blog posts on building an Asteroids game for the Xbox using F#. This prompted me to stop thinking about implementing an octree and actually get started.
Why F#? Well in this case it seems like the best tool for the job. I’d already considered a C# octree implementation on Code Project. Even after some clean up, refactoring (and bug fixing) I was less than happy with the clarity of the resulting code and ditched it.
The book actually includes some examples of n-body modeling and shows lots of examples of building trees with F#, something the language is pretty good at. As noted in my previous post I also discovered how to do TDD in F# which was a real help.
Looks like I’ll be speaking in San Francisco in February on the 22nd.
Using Agile with Large, Geographically Dispersed Development Teams
Distributed and large scale development are a fact of life for many teams. Unfortunately most agile methodologies or approaches assume that the team is located in a single team room. Until recently there has been little guidance about how to apply these approaches with a geographically dispersed or very large teams.
Ade Miller has been following an agile, distributed development approach for the past several years. During this time his teams within Microsoft have experimented extensively with different approaches to best address the challenges of distributed agile development and using agile on larger teams.
This meetup will address the challenges faced by large and geographically distributed agile teams and details some proven practices to address these issues and build successful distributed teams.
Definitely looking forward to this one! Great chance to talk to people outside of Redmond about how they do agile.
Dates for this year’s pattern languages workshop for parallel patterns have been announced. Not sure If I’ll be able to attend but it definitely looks interesting.
ParaPLoP 2010, a PLoP-style workshop on parallel programming patterns, will be March 30 – April 1 in Carefree, AZ. You are invited to submit a paper. Papers should describe one or more patterns, outline a pattern language, analyze previously published patterns, describe case studies of using patterns to develop parallel software, or present experience mining patterns from significant parallel code implementations.
Similar to PLoP, ParaPLoP will be organized as a set of writer’s workshops. ParaPLoP is extremely interactive and begins with the submission process. Submissions are due February 15, but if authors submit earlier, then they will receive feedback and can resubmit. Please visit our submit page for more information.
Space permitting, non-authors will be allowed to attend ParaPLoP 2010.
Here at patterns & practices we’re considering our options in terms of a follow-up on the PDC workshop. A book may be on the cards. If you have things you’d like patterns & practices to be doing in this space then post a comment here.
I spent a bunch of time over the holidays getting to know F# a bit better. I think I now consider myself to be truly dangerous with it.
A couple of things which repeatedly bit me as I stumbled through learning F# as a n00b. Read the rest of this entry »
The dates and venue for next year’s agile conference have been announced.
Agile 2010 is the leading international conference on agile methods in software development. Agile 2010 will be held in Nashville, USA. The conference brings together many disciplines in the fields of information systems and software development and bridges communities that rarely get a chance to exchange ideas and thoughts.
The conference will examine the latest theory, practical applications, and implications of agile methods.
And yes, that’s me on the right of the conference homepage playing with my laptop! This year there will be better Wi-Fi, I already bent the Conference Chair’s ear about it.
On another note… Why the ominous silence on the blog front. Been busy writing code. I now know enough F# to be truly dangerous. More on this real soon.
While I was at PDC Tibi Covaci interviewed me as part of his Five Minutes with… series. You can see the full interview here.
Ade Miller, manager of the Patterns and Practices group talks to Tibi about the history and possible future of parallel programming and how it will affect developers going forward…
Other than sharing my thoughts on parallel programming; past present and future you learn that; nuclear reactors may be less safe than you thought and five minutes with me is quite long enough.
Welcome to my blog on software development and probably a whole lot more. If you're looking for alpine climbing you'll find it on my climbing web site and blog.
