9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Man Hobby <manhobby8@gmail.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] Machine code programmers, assembly programmers and high level programmers
Date: Wed,  4 Apr 2018 14:21:32 -0300	[thread overview]
Message-ID: <CADF40MJyw5TkQ3Gq6Ov=14RDG4rf17uAPrDnayLX41wg=Buh_Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

Currently are employed experienceds machine code programmers?

If not, why?

Currently are employed novices machine code programmers?

If not, why?

Currently are employed experienced assembly programmers?

If not, why?

Currently are employed novice assembly programmers?

If not, why?

Currently the experienceds machine code programmers are paid especially
well compared to the high level programmers?

For example, currently the experienceds machine code programmers are paid
especially well compared to, say, a PHP, JavaScript, Java or C coding
position?

If not, why?

Currently the novices machine code programmers are paid especially well
compared to the high level programmers?

For example, currently the novices machine code programmers are paid
especially well compared to, say, a PHP, JavaScript, Java or C coding
position?

If not, why?

Currently the experienceds Assembly programmers are paid especially well
compared to the high level programmers?

For example, currently the experienceds Assembly programmers are paid
especially well compared to, say, a PHP, JavaScript, Java or C coding
position?

If not, why?

Currently the novices Assembly programmers are paid especially well
compared to the high level programmers?

For example, currently the novices Assembly programmers are paid especially
well compared to, say, a PHP, JavaScript, Java or C coding position?

If not, why?

I'm asking these questions because I really like the subject.

[-- Attachment #2: Type: text/html, Size: 1588 bytes --]

             reply	other threads:[~2018-04-04 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 17:21 Man Hobby [this message]
2018-04-05  9:42 ` Andre Wingor

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='CADF40MJyw5TkQ3Gq6Ov=14RDG4rf17uAPrDnayLX41wg=Buh_Q@mail.gmail.com' \
    --to=manhobby8@gmail.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).