![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
For example, a coder will add logging to their server code that tells them
what the server is doing. A programmer will add logging to their server
code that tells customer service what the server is doing. :-)
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> For example, a coder will add logging to their server code that tells them
> what the server is doing. A programmer will add logging to their server
> code that tells customer service what the server is doing. :-)
Are you using "coder" as a synonym for something like "hacker"?
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
> Darren New <dne### [at] san rr com> wrote:
>> For example, a coder will add logging to their server code that tells them
>> what the server is doing. A programmer will add logging to their server
>> code that tells customer service what the server is doing. :-)
>
> Are you using "coder" as a synonym for something like "hacker"?
>
No. A coder is someone who knows how to write code, but doesn't know how to
build an overall program. I used the term earlier here but I couldn't
remember where, so I didn't go look it up.
Coders are the people who say "I don't need to document my library, because
the code *is* the documentation." Or "here's documentation of all the
routines, but no documentation on the required order to call them, or what
happens when there's an error, or ..."
You get the coder vs programmer distinction in all fields, tho, as far as I
can tell. For example, in retail, it's the difference between "cashier" and
"salesman".
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> No. A coder is someone who knows how to write code, but doesn't know how to
> build an overall program. I used the term earlier here but I couldn't
> remember where, so I didn't go look it up.
Perhaps I would use the term "developer" instead of "programmer" in that
case. "Developing" a software usually entails more than simply writing its
source code.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
> Darren New <dne### [at] san rr com> wrote:
>> No. A coder is someone who knows how to write code, but doesn't know how to
>> build an overall program. I used the term earlier here but I couldn't
>> remember where, so I didn't go look it up.
>
> Perhaps I would use the term "developer" instead of "programmer" in that
> case. "Developing" a software usually entails more than simply writing its
> source code.
>
That works too. :-)
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New wrote:
> For example, a coder will add logging to their server code that tells
> them what the server is doing. A programmer will add logging to their
> server code that tells customer service what the server is doing. :-)
A proper software engineer will use logging to tell the user what has
happened and use trace for the service teams :-P
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |