public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Akbar A." <syedali011@earthlink.net>
To: <gcc@gcc.gnu.org>
Subject: info
Date: Tue, 09 May 2000 11:56:00 -0000	[thread overview]
Message-ID: <DBEJKMEBBLEKDCBLJDBPMEBJCEAA.syedali011@earthlink.net> (raw)
In-Reply-To: <309F4FC4705DC844987051A517E9E39B16EEBB@red-pt-02.redmond.corp.microsoft.com>

hello.
well I am _LEARNING_ a lot of info from gcc and it's source code. It seems
that all i have been doing ;)
my question is this, if you give away your source code isn't it possible
that your competitors could see what you are doing?
i know i am not a political person i am just a programmer, but how does that
work?
sorry for being o.t. it just seemed like a lot of you make a living off
opensource code and working with companys that do not offer an ipo.
do people pay you to write software code?
isn't that what the company's employess are for?
like my sister gets paid 44,000 us dollars every year to write manuals for
adobe photoshop 5.0 ("technical writer") _EVEN_ though there is already
awsome one in the online help in most of the works she writes about. she
told me that the people that work with at the company are too arrogant to so
and "look for online help". is this true? i guess what i need is a second
opinion.
But she also does a lot of bank software technical writing as well.
again. sorry for being so o.t
please e-mail me directly.
peace,
akbar A.

  parent reply	other threads:[~2000-05-09 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-09 10:25 rfc: new libgcc build mechanism Donn Terry
2000-05-09 11:42 ` Felix Lee
2000-05-09 11:56 ` Akbar A. [this message]
2000-05-09 14:02   ` info Martin v. Loewis
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 15:01 info fredy.pena
2003-09-10 10:24 Info TKostadinov
2002-04-01  2:34 info alex bohemia
2002-04-01  4:52 ` info Bryce McKinlay
2002-04-07 14:13   ` info Tom Tromey
2001-03-08 14:01 Info Marco Mangiante
2000-05-09 14:49 info Mike Stump
1999-10-27  0:32 info TAXhotpop
1999-10-27 12:16 ` info Martin v. Loewis
1999-10-31 23:35   ` info Martin v. Loewis
1999-10-31 23:35 ` info TAXhotpop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DBEJKMEBBLEKDCBLJDBPMEBJCEAA.syedali011@earthlink.net \
    --to=syedali011@earthlink.net \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).