The subtle art of punting.

Summer is nearly upon us, so it’s time to give some gentle instruction to the newbies on the subtle art of punting in Cambridge.

For the beginner:

  • We punt from the back here in Cambridge. This is not Oxford.
  • Lift the pole up, and drop it over the side. Gingerly lowering it in does not work. If the punt is moving forward you can pretty much drop it vertically.
  • You will immediately know whether it’s struck bottom, how deep it is, and whether your pole is caught in weeds, or has bounced off the concreted edges.
  • Do not use the pole as a paddle. That doesn’t work either.
  • Push. This requires some oomph. Try to stop pushing before you’re bent double.
  • Remove the pole from the bottom. If it’s weedy (going granchester way), the trick is to twist the pole as you pull, and it should come out easy. If it doesn’t, then let go and stay in the punt. The alternative is wet, and they give you a paddle.
  • Once you’ve pushed, got the pole back, and are moving, then you can use the pole as a rudder.

More advanced tips:

  • The angle at which you drop the pole in is quite important. Angle it away from the punt as you drop it to move towards the bank, and under the punt (yes, underneath your feet) to move toward the centre. This is why the beginners always end up going in circles.
  • Once you get confident, you’ll find that after dropping the pole, you can guide it pretty much one-handed, and face forward, not sideways. Quicker that way, and fewer splinters too.
  • When pushing (if facing forward), you can lean back quite a long way, it looks more stylish that being bent over, faster too.
  • No splinters with metal poles.



A couple of minor updates to what’s currently on this site:

Indexed Store:

Index nodes now have OtherNode and IndexLink properties. This allows Index nodes and Search Vals to get hold of the corresponding IndexLink class, which contains the Index Tag, so you can do meta-comparisons based on the tag of the index, not just the data and index node class type.

Fixed a minor bug to do with indices allowing duplicate values. The index searching should be slighty different depending on whether one is adding, searching or deleting to the store.

Work Items:

Fixed an obscure race condition where client software attempts to free work items before the completion handler has finished. Programmers are unlikely to do this directly, but it’s still possible if completion handlers use TThread.Queue. Workitem destructors now use refcounts.

Anything else?

Yes, I’m still working on that extra special piece of software.