I will give you a way to get further forward mate.... Follow my transom
around the course. :-)
-----Original Message-----
From: Robert Harper [mailto:rharper@xxxxxxxxxxxx]
Sent: Wednesday, 12 September 2007 4:22 AM
To: swiftsolo@xxxxxxxxxxxx
Subject: Re: Rudder rip-off
Bram, one more thing you might think of is to add a "DON'T DO THIS" link
where you explain some of your failed attempts. I've found that sometimes
knowing what not to do is more important than what to do. Only posting
what you currently feel is the best case and saying this is the rule,
forces the Canucs and Aussies to buck the trend and go their own way. If
you show them the things that you've discarded, they'll have a better idea
of what to do to take us farther forward.
On Tue, 11 Sep 2007 12:40:15 -0600, <BDally6107@xxxxxxx> wrote:
>
> You did good Karl! Actually, I responded to him already. Knowing
> Dave, I
> suspect his transom bar comment was a bit tongue-in-cheek. I deny
> (almost
> entirely) that the bar was added because I had some left over wood.
> As I pointed out, I use colors when I intermix my text with the
> builder's.
> If I don't and I backspace while I'm writing, AOL will eliminate the
> little
> arrows that indicate the original post. Once that happens, I use color
> to
> separate the two. For the Canooks, I'll use pink in the future (to
> show my
> sensitivity).
> Actually, the point of my comments was to use the opportunity to save
> builder's in general a lot of grief. Examples?
> 1. building launcher throats without hybrid
> 2. building blades over foam with little or no hybrid (also, not
> following
> the other instructions in the PDF)
> 3. moving deck hardware without regard to the impact on other systems (
> I've been guilty of this one far more times than I'll admit)
> 4. Installing spreaders that are too long and not raked properly.
> 5. Making spreaders using a number of untried and unsuccessful
> lay-ups/methods.
> 6. Mast builders failing to follow the specific instruction to use
> Plexus
> 425 to bond the track
> All of the above have led to failures. Some of the failures have led to
> posted ideas on how to avoid the problem in the future (except "follow
> the
> original friken instructions" is only occasionally the suggested
> solution).
> Please realize that I've spent a lot of time over the last seven years
> on R&D
> and had already made many of these mistakes before writing the manuals
> (there
> are a couple of exceptions). My intention with all of this is to get
> everyone
> to spend your time improving from the current state of the art instead
> of
> working to find systems and methods almost as good. Without trying the
> status
> quo, you'll likely not know which of the two you are engaged in.
> Bram
>
>
>
> ************************************** See what's new at
> http://www.aol.com
--
Live large, love lots, and sail fast!
The mark of who you are is determined by what you do when you don't have
to do it.
USA 050 Fugu
77959 Wasabi
Robert Harper
This is the Swift Solo mailing list. For unsubscribe instructions,
visit here: http://catzooks.com/swift-solo/
This is the Swift Solo mailing list. For unsubscribe instructions,
visit here: http://catzooks.com/swift-solo/
|