DISQUS

I am actually using Globetrotter Connect again, it's working just fine. I am on version 1.3.0 (d163)

Hej Denise,

Kolla med Ola Ellnestam på Agical om det finns platser kvar. Det är på deras kontor på Västerlånggatan.

Måns, why mix 'should' and 'test'? To me that sounds like the 'test' once are written after the implementation, I am wrong?

Torbjörn, I totally agree with the notion that 'should' encourages dialog. Use it as much as possible when discussing features. However, the specs also acts as documentation of design decisions, and as such they should convey as much information as possible.

Steve,

BDD is all about conversation, and people already have their own definition of 'should'. Let's work with that instead of redefining the meaning.

Kedar, thanks! I sincerely hope that we will need your help soon :).

I must be totally backwards. Back in my early Java days, I actually organized packages by feature. After reading Eric Evans book on DDD I changed my style to by layer, which I find a lot better.

My problems with the by feature way of doing things normally involved granularity of features - is the thing we are building a new feature with its own package or should it a part of another package. Also, as others have mentioned, some things are cross cutting meaning that you either create the dreaded 'common' package, or just chuck it into the package you feel it belongs to the most.

Jeff,

Thanks for your comment. After this incident I have refrained from commenting on Cedrics writings. Not all gems in the Google mine I presume.

@Marco: If I find the DVD I burned I can make the image available to you, but I am not sure I have it anymore.

@Ashish - sounds like a worthwhile endeavor

@Pat: Great hearing from you! I will not make it to XP2008 though, but I will most probably be in London somewhere around the same time as you - this time beers are on me.

@Aslak:

You are absolutely right.

And thanks :).

@Jimmy: Thanks, I appreciate it.

@Mathias: The pleasure has been ours. I will especially miss the burger lunches :).

@Erin: I sure hope so. I am supposed to come to London June 4th and stay for a week, and hopefully Cecilia will join me.

@Muness: Thanks, I appreciate it :).

@Mikael: Tack!

@PR-hajen: :)

@steven: Thanks!

@behe Thanks :)!

@blah: You are really making our point here.

Brilliant - one of the best pieces I have read on SOA.

@ctran:

Thanks for noticing. I had actually written it correctly, but Markdown treated the underscore as "begin italics" since I did not escape it. Fixed.

Jon, that is actually quite comforting to hear :)

It turns out that a bunch of people that got the mail has signed up with TripIt, so I now have a bunch of friends there. Oh well.

Tobias:

I would not say that the Scrum I know per definition includes any other engineering, rather that it encourages doing so. This small difference makes a lot of people ignore it.

I haven't updated my Scrum knowledge the last year though, perhaps this has changed?

At the time I wrote this I was involved in projects where the archicture was not testable. This disallowed test suites of any kind, making every release depend on lots of human testing. The process used lacked a lot of agility.

But still the teams told me "but we are doing Scrum", which caused the blog post. And of course you are right, many people are used to prescriptive methods.