3 ms·

No, no. Compilers don’t write (their own) code, they translate (our) code.

• growse 7y ago
  > No, no. Compilers don’t write (their own) code, they translate (our) code. No, no. Developers don't write (their own) code, they simply translate the (customer's) specifications.
  • Gibbon1 7y ago
    > simply translate the (customer's) specifications. LOL no! If I did that my customers would go out of business.
• Stratoscope 7y ago
  It was an allegory. A metaphor. A silly story. Here is a true story. When I first started programming, we were told that professional companies developed software as follows. (Of course we were a scrappy timesharing startup, so we took shortcuts, but this is what we were told the pros did.) • A systems analyst took business requirements and created a specification. • A programmer took the specification and used it to draw flowcharts. • A coder took the flowcharts and converted them into code in a particular programming language, hand-written on coding forms. • A keypunch operator took the coding forms and punched the code onto cards. Pop quiz! Who actually wrote the code: the programmer or the coder?
  • xaedes 7y ago
    The keypuncher?
    • Stratoscope 7y ago
      You may be closer to the mark than you realize. A good keypunch operator wouldn't just type in your code, they would also do some basic sanity checks on it, and either fix some of your bugs as they punch, or hand you back your coding form with some notes marked on it. After all, you didn't want to have to wait many hours or a full day to get back your card deck and printout to find what you did wrong. When you found a keypunch operator like that, you would seek them out every time, maybe even bring them little gifts. Of course now we are all our own keypunch operators!