Code H’yung: Ropes, Sprint 6

Welcome to the Sprint 6 Review of the Ropes h’yung mini-project. As the only person who really matters on this project, I’m happy to report that we have code to show you for our review today!

Recall from Sprint 5, Sprint 6′s agenda:

• finish testing and debugging hasMore
• start to implement renumber

I am Developer, Born Brave.

The building is creaking. The machine isn’t working. The imps in the teleportation lab need to be exterminated. Any metaphor applies.

Code H’yung: Ropes, Sprint 5

Welcome to the Sprint 5 Review of the Ropes h’yung mini-project. As the only person who really matters on this project, I’m happy to report that we have code to show you for our review today!

The official blog observer just told me that maybe I should stop referring to this h’yung as a mini-project, since it is by far the longest-living project on this blog. He might be right.

The goals for this Tea Party-shortened sprint were:

• refactor next
• implementation of endPointsOf:aString method
• start to implement renumber

The first two goals are nearly complete. As my scrum-master at work would say, we are carrying over testing into the next sprint. Due to the vacations that our developer took this sprint, we had to put renumber on the back burner.

Indeed. So let’s recall what next looked like at the end of the last sprint:

Code H’yung: Ropes, Sprint 4

Welcome to the Sprint 4 Review of the Ropes h’yung mini-project. As the only person who really matters on this project, I’m happy to report that we have code to show you for our review today!

The goals for this sprint, way back before Cruise Control mode:

• implement parent and sibling
• I actually already started, so continue implementation of RopeNodeIterator
• implement renumber

The first two objectives were met. The lesson re-learned during this sprint: even the seemingly simplest things can grow tentacles that you never imagined before.