Wednesday, July 20, 2011

Feature Branching vs. Continuous Integration

Monkey thinker

I posted my thoughts to the topic of Feature Branching vs. Continuous Integration some month ago.

Now here is a very good video interview where Mike Mason and Martin Fowler characterize Feature Branching and the problems that may result from it and where they see that Feature Branching is applicable and where it is not recommended.

And here is an experience report by Sarah Taraporewalla that describes sarcastically the problems you get into with Feature Branching.

The conclusion I take away from that:
Feature Branching is good for loosely coupled collaboration typically found in open source projects. Feature Branching is not recommended for dedicated teams with tight collaboration, which is the type of collaboration you are striving for in a typical Scrum project.


Update 2011-08-14:

Interesting points from the above interview are:

  • The pain from merging increases exponentially with the age of your branch.
  • In practice feature branches discourages refactoring: You are not improving the core codebase when working on a new feature, because you are afraid of merging those core refactorings back later. You rather build your feature around the existing core, as it is, living with its shortcomings...
  • Alternatives are feature toggles and branch by abstraction (archtiectural branching)
  • Using feature branches for organizational control is a sign of a dysfuntional environment. If you don't trust your team to commit frequently, then you have a problem that can't be solved with a version control system.

Related is the article by Martin Fowler describing Semantic Conflicts. The main conclusion there is that tools only can support in merging textual conflicts but they can never solve semantic conflicts.

Sunday, July 17, 2011

Quotes of the Week: JavaScript

quotes2.jpg

A very large group of developers still thinks of JavaScript as a joke.

 

JavaScript is Assembly Language for the Web.
JavaScript is the ugly duckling among programming languages. It takes time to embrace it and discover its beauty.

Javascript is fast becoming a serious contender to Ruby and JVM languages.

After almost a decade of the ruby community being the web innovation lead, it really looks like the javascript community is taking over.

 

Thursday, July 14, 2011

Kindle = Free Internet Access

Kindle Recently I bought a Kindle 3G. I am living in Switzerland and I bought it from Amazon.com.

Amazon offers free internet access with this device over the cellular network. Everywhere, globally. The goal is that you can access the Kindle shop and buy books everywhere on the world.

The Kindle has also a built in web browser that you can use to access the internet.
Now the question is: Can you browse the internet for free everywhere on the world with your Kindle?
This is not completely clear from Amazons product description and there are different contradicting reports floating on the internet. To help to clarify the topic here my experience:

Last month I was in Norway, Singapore, Bali and Lombok and everywhere I could access the internet for free without a problem. It was not always a 3G connection, it worked also over EDGE and GPRS.

Of course the browser experience on the Kindle is not comparable with other mobile devices: It is quite slow and cursor navigation has to be done with the cursor buttons. Also typing on the kindle keyboard is quite cumbersome.

Nevertheless I think this is an invaluable feature of the Kindle!

I was primary using Gmail, Google Reader and Twitter. Through their mobile interfaces those sites are definitely usable on the Kindle and this was a comfortable (and cheap) way to stay at least minimally connected throughout my vacation.

Tuesday, June 28, 2011

Quotes of the Week: The Enterprise

quotes2.jpg

Events such as the Rails Rumble have shown that it’s possible to finish software projects in two days that might take a corporate development team weeks or months in a normal project scenario.



Scott: What is the penetration of Node.js into the "enterprise"?
Tim: It depends on what you mean by "enterprise"?
Scott: Large, slow moving corporations.


The corporate environments are awful!

 

In corporate environments the product don't have to be good. Sometimes they don't even have to exist ... if you are a thoughtful developer, you are in the wrong place!

 

Fear leads to Risk,
Risk leads to Process,
Process leads to Hate
... and suffering and Gant-Charts.
- Dan North, Keeping Agile Agile

 

Tuesday, June 14, 2011

Vacation Book & Screencast List

This is my book list for my current four weeks of vacation:

Bhh5 xlargecoverTbcoffee xlargebetaNrtest xlargecoverCfcar2 xlargecover51ZmBE4huJL BO2 204 203 200 PIsitb sticker arrow click TopRight 35 76 AA300 SH20 OU0151KQ2P7V1RL SL500 AA300

The last one I am taking along old-school-dead-tree, the rest I bought as ebooks to read on my kindle.

Also I am looking forward to watch the recent tekpub and peepcode episodes:

Ft sullivan slideMvc3 slideNode js coverPlay by play jbarnette titleEventmachinePostgresql

... as well the latest railscast episodes.

Saturday, June 11, 2011

Our NDC 2011 Slides: SpecFlow & BDD

Here are the slides from the two presentations Gaspar and I did last week at the Norwegian Developers Conference 2011.

The videos should be published soon on the NDC homepage.

Tuesday, June 7, 2011

Rethinking the Test Automation Pyramid

The Test Automation Pyramid is an analogy that is often referred when discussing test automation:
Pyramid orig WB
I believe the origin of this analogy is referred to Mike Cohn. At least he discussed it in the agile context in his post The Forgotten Layer of the Test Automation Pyramid. If you google for "testing pyramid" you find many derivations of the original pyramid picture. While preparing for our BDD presentations at the NDC, Gaspar and I were discussing the pyramid once again. And we also came to the conclusion that we want to redraw it:
Pyramid new WB
We found that we want to decouple test automation from architectural layering.
On the one hand we found that the tip of the pyramid is not always UI testing. Of course this depends on your definition of UI. But in a lot of systems I have seen interactive testing that is not really going through a UI (e.g. checking the print-layout of a report, checking if files are delivered on a share ...)
On the other hand we feel that with modern approaches (and tooling) automated UI testing can also be done efficiently in the middle layer of the pyramid to perform functional tests. The Rails/Capybara/Cucumber stack is a good example for this.

The next question is, if the functional slice of the pyramid should once again divided in different sub-slices. On the lower level there are automated Scenarios that usually fit to one feature of the system.
The ThoughTworks technology Radar from January 2011 mentions Journeys as a more holistic approach that describe and verify coherent functionality overarching individual scenarios. This will be an interesting concept to explore ...

Of course we were not the first to discuss this, there are other posts about this.
Related Posts Plugin for WordPress, Blogger...