Update: Distributing media can be problematic. If you’ve read the comments below, I’m sure you agree that I’ve had my fair share of difficulties. There have been two issues that I’ve been struggling with recently; (a) the format that I was using (avi’s) only worked on some machines; and (b) the files were not always accessible.
To address the first problem, I’ve converted the orginal avi’s to mp4’s. I’ve tested the mp4’s under VLC and they play without any problems. The original avi’s still work with Windoze Media Player. The bad news is that neither format works with Quicktime. I’m inexperienced with QT and I’m out of options at this point. I’m open to suggestions on how to resolve this, if you have any.
To address the second problem, I’ve moved the files to a new (hopefully more reliable) host. The host also offers torrents, and that’s available as well. So, here are the screencasts:
Individual avi files:
- Intro to TDD (Session 1) [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
Individual mp4 files:
- Intro to TDD (Session 1) [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
- TDD with Ruby (Session 2) Part 1 of 4 [link]
Now, back to the original article …
My previous screencast [1] was a simple introduction to TDD with Ruby. The intention was to demonstrate TDD and not much else. Having done that there are a number of other topics that I feel need to be addressed including exceptions, database interaction and mocks.
In this screencast I’ve focused on TDD with exceptions and error handling.
Read the rest of this entry »
Filed under: Ruby, Screencasts, TDD, Test Driven Development
[Update: This is part 2 of a four part series. Here are links to part 1,
part 2, part 3 and part 4.]
As Agile methodologies gain wider acceptance, they will be taken up by larger numbers of organizations. The question of how to introduce an Agile methodology into an enterprise with the least amount of risk will become more and more common. The two approaches that are typically talked about are Top-Down, where senior management take the initiative to introduce Agile, and Bottom-Up where developers and testers take the initiative to introduce Agile.
The truth of the matter is that both of these approaches have flaws. The successful approaches that I’ve witnessed have used some combination of both the Top-Down and Bottom-Up approaches. Agile software development practices can force large changes in the corporate culture, and making the change to an Agile organization is only possible if there is support from all parties involved.
Ultimately, there needs to be some coordination of both these efforts. There needs to be some planned approach to deal with concerns raised by those who do the work, in addition to those who lead the organization and make the strategy a reality.
Read the rest of this entry »
Filed under: Agile Software Development, Cultural Change, Organisation Change, Planning, Project Management, Scrum
Update: This is part 1 of 2. You can find the second part of this series here.
Test Driven Development (TDD) is something that many people talk about but few actually do. A common misconception is that TDD is about writing acceptance tests before developing the code. It’s really more than automated acceptance tests … it’s about using unit tests to drive the development process.
There are several books ([1] and [2]), good written tuturials using java [3] and even a tutorial using Ruby [3]. But I find it’s very difficult to communicate how TDD should feel using the written word. In an attempt to help bridge the gap, I’ve created some screencasts that demonstrate TDD.
Read the rest of this entry »
Filed under: Ruby, Screencasts, TDD, Test Driven Development
Recent Comments