Re: Using Vine in 3-way interactions (was Re: Question on redirectors/whenMoreResolved in the 3-way case, in the middle vat)
Mark Miller <[email protected]> Sat, 7 Mar 2015 18:04:23 -0800
| Newsgroups | gmane.comp.lang.e.general |
|---|---|
| Message-ID | <CAK5yZYiqaGom=XwYjP0J2zUNON_0N_k_qvto6=StB_Bk=dro4w@mail.gmail.com> |
--===============5708361376487249975== Content-Type: multipart/alternative; boundary=bcaec548a0551ceadb0510bd56d9 --bcaec548a0551ceadb0510bd56d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Mar 7, 2015 at 4:53 PM, Rob Withers <[email protected]> wrote: > Sorry, I made the assumption! you had heard of them. They are from a > little book called The Four Agreements, by Don Miguel Ruiz: > http://www.amazon.com/The-Four-Agreements-Practical-Personal/dp/187842431= 9 > . > Hi Rob, I hadn't heard of them. Since we're talking about captp, with tongue only slightly in cheek, I'll venture a reinterpretation of them as best practice advice for writing an agent to participate in a distributed secure system of mutually suspicious agents. > > They are: > =E2=80=9CThe First Agreement: Be Impeccable with Your Word > (Integrity) Don't be malicious. Meet your protocol's / api's / type's contractual obligations. Don't lie. > > The Second Agreement: Don=E2=80=99t Take Anything Personally > When another agent seems to violate its contract, remember that it may not be a targeted attack against you. It may just be buggy. Or your contract conformance test may be buggy. (Like Heinlein's razor <http://muchow.dk/ttrttc/?p=3D565> but without the derogatory language. There are plenty of bugs in the world, and we've all caused them.) > The Third Agreement: Don=E2=80=99t Make Assumptions > (Loose coupling) Your agent's correctness should rely as little as possible on assumptions about the behavior or state of other agents. > > The Fourth Agreement: Always Do Your Best=E2=80=9D > (Availability) If the first agreement corresponds to integrity/safety/consistency, this one corresponds to availability/liveness/progress. In a distributed system, no one can guarantee that they will continue to provide good service to well behaved clients, but one should strive to provide good service as often as possible= . > > > https://experiencelife.com/wp-content/uploads/2011/11/28-the-four-agreeme= nts.pdf > > I suspect many other valid bits of interpersonal and folksy advice can be translated into software engineering best practices. After all, we're all dealing with many of the same abstract coordination problems. --=20 Cheers, --MarkM --bcaec548a0551ceadb0510bd56d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>On Sat, Mar 7, 2015 at 4:53 PM, Rob Withers <span dir= =3D"ltr"><<a href=3D"mailto:[email protected]" target=3D"_blank= ">[email protected]</a>></span> wrote:<br></div><div class=3D"g= mail_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st= yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb= (204,204,204);border-left-style:solid;padding-left:1ex"> =20 =20 =20 <div bgcolor=3D"#FFFFFF" text=3D"#000000"> Sorry, I made the assumption! you had heard of them.=C2=A0 They are fro= m a little book called The Four Agreements, by Don Miguel Ruiz: <a href=3D"http://www.amazon.com/The-Four-Agreements-Practical-Personal/dp/= 1878424319" target=3D"_blank">http://www.amazon.com/The-Four-Agreements-Pra= ctical-Personal/dp/1878424319</a>.<br></div></blockquote><div><br></div><di= v>Hi Rob, I hadn't heard of them. Since we're talking about captp, = with tongue only slightly in cheek, I'll venture a reinterpretation of = them as best practice advice for writing an agent to participate in a distr= ibuted secure system of mutually suspicious agents.</div><div><br></div><di= v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px= 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left= -style:solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000"> <br> They are:<br> =E2=80=9CThe First Agreement: Be Impeccable with Your Word </div></blockquote><div><br></div><div>(Integrity) Don't be malicious. = Meet your protocol's / api's / type's contractual obligations. = Don't lie.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl= e=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(2= 04,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor=3D"#FFFF= FF" text=3D"#000000"> <br> The Second Agreement: Don=E2=80=99t Take Anything Personally </div></blockquote><div><br></div><div>When another agent seems to violate = its contract, remember that it may not be a targeted attack against you. It= may just be buggy. Or your contract conformance test may be buggy.</div><d= iv>(Like Heinlein's razor <<a href=3D"http://muchow.dk/ttrttc/?p=3D5= 65">http://muchow.dk/ttrttc/?p=3D565</a>> but without the derogatory lan= guage. There are plenty of bugs in the world, and we've all caused them= .)</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p= x 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bo= rder-left-style:solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#0= 00000"> <br> The Third Agreement: Don=E2=80=99t Make Assumptions </div></blockquote><div><br></div><div>(Loose coupling) Your agent's co= rrectness should rely as little as possible on assumptions about the behavi= or or state of other agents.</div><div>=C2=A0</div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le= ft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bg= color=3D"#FFFFFF" text=3D"#000000"> <br> The Fourth Agreement: Always Do Your Best=E2=80=9D<br></div></blockquot= e><div><br></div><div>(Availability) If the first agreement corresponds to = integrity/safety/consistency, this one corresponds to availability/liveness= /progress. In a distributed system, no one can guarantee that they will con= tinue to provide good service to well behaved clients, but one should striv= e to provide good service as often as possible.</div><div><br></div><div>= =C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0= .8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s= tyle:solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000"> <br> <a href=3D"https://experiencelife.com/wp-content/uploads/2011/11/28-the-fou= r-agreements.pdf" target=3D"_blank">https://experiencelife.com/wp-content/u= ploads/2011/11/28-the-four-agreements.pdf</a><div><div class=3D"h5"><br></d= iv></div></div></blockquote><div><br></div><div><br></div><div>I suspect ma= ny other valid bits of interpersonal and folksy advice can be translated in= to software engineering best practices. After all, we're all dealing wi= th many of the same abstract coordination problems.</div><div><br></div><di= v>=C2=A0</div></div>--=C2=A0</div><div class=3D"gmail_extra"><div class=3D"= gmail_signature">=C2=A0 Cheers,<br>=C2=A0 --MarkM</div> </div></div> --bcaec548a0551ceadb0510bd56d9-- --===============5708361376487249975== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ e-lang mailing list [email protected] http://www.eros-os.org/mailman/listinfo/e-lang --===============5708361376487249975==--