Path: utzoo!attcan!uunet!lll-winken!brutus.cs.uiuc.edu!zaphod.mps.ohio-state.edu!think!mintaka!ogicse!blake!ramsiri
From: ramsiri@blake.acs.washington.edu (Enartloc Nhoj)
Newsgroups: comp.sys.atari.st
Subject: Re: Becoming an Official Atari Developer!
Keywords: Atari Corp, ST
Message-ID: <5754@blake.acs.washington.edu>
Date: 14 Feb 90 17:35:13 GMT
References: <489b42d9.14a1f@force.UUCP>
Reply-To: ramsiri@blake.acs.washington.edu (Enartloc Nhoj)
Organization: University of Washington, Seattle
Lines: 28

In article <489b42d9.14a1f@force.UUCP> covertr@force.UUCP (Richard E. Covert) writes:
>The following are notes about becoming an Official Atari ST Developer in
>
>I called Gail Johnson in early January 1990 to inquire about becoming an Official
>Atari ST/TT Developer. I was sent a large envlope withing a week. The envelope
> Richard E. Covert, Lead Engineer of Software Tools Group
> AG Communications Systems, Phoenix AZ   (602) - 581-4652
> TCP/IP: covertr@gtephx
> UUCP: {ncar!noao!asuvax | uunet!zardoz!hrc | att}!gtephx!covertr


I had the identical experience recently.. and my opinions
were much the same as Richard's.

Frankly, condidering
the state ATARI is in these days...
Seems more reasonable to make the developer's kit
robust, cheap and thorough.  

ATARI needs to attract as many good developer's
as possible.  All i read regarding developer
support is a great sense of frustration and
resultant indignation.

Can ATARI "afford" to be this way?

-kevin
ramsiri@blake.acs.washington.edu