ISerializable - Roy Osherove's Blog

I think I heard Jerry Seinfeld say that the life of an actor are:

Which really feels these days like:

• What’s “CMM”
• Let’s do “CMM”
• Let’s do an adapted version of “CMM”
• Here’s a better,lighter “CMM”
• What’s “CMM”?
• What’s “Agile”
• Let’s do “Agile”
• Let’s do an adapted version of “Agile”
• Here’s a better, lighter “Agile”
• What’s “Agile”?
• What’s “Scrum”
• Let’s do “Scrum”
• Let’s do an adapted version of “Scrum”
• Here’s a better, lighter “Scrum”
• What’s “Scrum”?
• What’s “Lean”
• Let’s do “Lean”
• Let’s do an adapted version of “Lean”
• Here’s a better, lighter “Lean”
• What’s “Lean”?

I’m half way through JQuery in Action and have to say I was pleasantly surprised to read a lot of things about the “why'” things are the way they are, and not just simple facts about JQuery.

Lots of useful information, especially for a web newbie like me (I used to hate html related activities until $() came along)

Way to go, great book!

My upcoming TDD Master class in Oslo, Norway, during august, has only a few seats left. I heard from several people at NDC that they are planning to sign up, so I’d suggest they hurry up.

This class is a 5 day pair programming fest, where people work together on Unit Testing and TDD related excercises with my coaching.

It’s the class I wish I had done 10 years ago.

• If you’re interested in me doing this class in other countries, drop me a line.
• If you’ve already been to my class, I’d love it if you left your thoughts, comments or recommendations to it on the comments to this post. I will later use them on other places that talk about this class (with your name next to it!)

NDC 2009 was a blast!

Thanks for all the great conversations :)

Here’s what it looked like when you look up at a full room in NDC

here are the questions that teams and team leads should be asking themselves on a daily\weekly basis.

There are more, but these are the basics, to me. It’s part of the summary for the talk “Beautiful teams I am giving at SEConf and NDC. we do a lot of this stuff over at work, and it’s proving itself on a daily basis.

Whole team

1. What can we automate?
2. where are we "Reinventing the wheel"?
3. what are the tools that slow us down?
4. what tools can we use better?
5. are there bugs that I could have found earlier? how do I make sure I find them earlier?
6. when do we find out we built the right thing?
7. when do we find out our code\design sucks? how can we make that earlier?
8. How do we show progress at the team level? at the management level?
9. How many meetings does each dev have every week? how can we remove them?
10. Are we building by feature or by layer?
11. can we make all our team sit in the same place?

Team Lead

1. daily: what bottlenecks exist in the team? what have I solved?
2. will my devs be better in a month or two than they were before? if not, how do I make that happen?
3. what prevents my devs from working? what am I doing about this?

This was such a beautiful picture, I just had to share.

My beautiful Itamar, eating Pitanga on a trampoline.

My book, The Art Of Unit Testing, is now in stock at Amazon. If you’ve read the book, I’d love it if you put in a review on that page.

wow. I didn’t even know these sorts of sites existed!

Isn’t the web great for really small niche markets?

(via Jason)

What are your thoughts on this style of writing?

• Specifically the “Explicit” way of defining arrange, act and assert scopes.
• also, given the name of the test, where should the call to “OnApplyTemplate” be (if you’ve never seen the code)?
• which version makes more sense to you? A, or B?

version A:

version B:

Coming up in SilverUnit, the true unit testing framework for silverlight controls