home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.programmer:7430 comp.os.os2.advocacy:11929
- Path: sparky!uunet!olivea!gossip.pyramid.com!pyramid!octopus!sjsumcs!rick
- From: rick@sjsumcs.sjsu.edu (Richard Warner)
- Newsgroups: comp.os.os2.programmer,comp.os.os2.advocacy
- Subject: Re: Why you should get everything in writing (long)
- Message-ID: <1993Jan8.160909.16042@sjsumcs.sjsu.edu>
- Date: 8 Jan 93 16:09:09 GMT
- References: <1ii7alINNon4@controversy.math.lsa.umich.edu> <1993Jan7.220154.446@fcom.cc.utah.edu> <1993Jan8.002640.5554@gandalf.UMCS.Maine.EDU> <1993Jan8.031151.9438@cs.brown.edu>
- Organization: San Jose State University - Math/CS Dept.
- Lines: 25
-
- wcn@cs.brown.edu (Wen-Chun Ni) writes:
-
- >In article <1993Jan8.002640.5554@gandalf.UMCS.Maine.EDU> jurlwin@gandalf.UMCS.Maine.EDU (Jeff Urlwin) writes:
- > <stuffs from Robert and Brian deleted>
-
- >Based on the impression, I believe that he should have be going through
- >a very long period of frustration dealing with IBM. Jeff is right.
- >The most urgent thing is to encourage IBM to do anything legal to
- >bring Robert back if IBM does want the support of developers. Note
- >that the single event occurring to Robert may be very serious to IBM's
- >image. We may blame Robert for being naive when dealing with some
- >guy in IBM without writing anything down. The fact is, how could you
- >expect a software developer to know everything about the future trouble.
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
- In this case he was more than a developer, he was an independent
- businessperson. One of the first things taught in business schools is
- that everything should be put in writing. This was HIS failure, not
- IBM's. Without a written agreement, he has no leg to stand on.
-
-
- >Wen-Chun Ni, wcn@cs.brown.edu (401) 863-7669
- >-------------------------------------------------------------------
- > I do more after 2 a.m. than most people do all day.
- > - from a T-shirt given by a friend.
-