2 ms·

Who cares who's a good programmer and who's not? The poor soul who has to maintain your crap. it doesn't matter as long as I end up with a product people want

by edw519 17y ago

Who cares who's a good programmer and who's not? The poor soul who has to maintain your crap. it doesn't matter as long as I end up with a product people want to use It does matter when it comes to maintaining that code base. When maintaining crappy code, only bad things can happen: 1. It takes too long. 2. It costs too much. 3. It doesn't get done at all. "cool stuff" and "completely inept" are contradictory terms. You may not care, but enough of us do that you should get better at your craft and spare the rest of us.

unalone 17y ago
You're making the assumption that I code things that require maintenance from other people, and that I code for a living. I code for fun, and I make small things that other people happen to enjoy, things simple enough that once I get them working the first time, they don't break. When I work on major projects, my partner's the programmer, not me.
- olliesaunders 17y ago
  Language designers want to create languages that professionals will use. Maintenance is a problem for any professional. You're lucky not to have to deal with that problem but that doesn't mean language designers are mistaken for engaging in attempting to find a solution to that problem just because it doesn't affect you.
  - unalone 17y ago
    Please let me answer you in one thread before you repeat your counterargument. I've answered this as you posted this second one.
dkersten 17y ago
Well, if the code thats produced is good, then I agree with unalone - it doesn't matter if the programmer is good or not. Of course, if the code IS bad, then sure, but would that not kinda go against what I was saying in my comment? Its all about solving a problem in the simplest, cleanest, most complete (ie, the problem isn't solved when corner cases are ignored) way. If a language is truely good, it will help programmers, good and bad, to achieve this. If the bad programmer then manages to produce good code, then (s)he is indistinguishable from a good programmer. (The difference between the two then becomes that the good programmer can do this with most problems, while the bad one with only a subset).

by edw519 17y ago

unalone 17y ago

You're making the assumption that I code things that require maintenance from other people, and that I code for a living. I code for fun, and I make small things that other people happen to enjoy, things simple enough that once I get them working the first time, they don't break. When I work on major projects, my partner's the programmer, not me.

olliesaunders 17y ago
Language designers want to create languages that professionals will use. Maintenance is a problem for any professional. You're lucky not to have to deal with that problem but that doesn't mean language designers are mistaken for engaging in attempting to find a solution to that problem just because it doesn't affect you.
- unalone 17y ago
  Please let me answer you in one thread before you repeat your counterargument. I've answered this as you posted this second one.

dkersten 17y ago

Well, if the code thats produced is good, then I agree with unalone - it doesn't matter if the programmer is good or not. Of course, if the code IS bad, then sure, but would that not kinda go against what I was saying in my comment? Its all about solving a problem in the simplest, cleanest, most complete (ie, the problem isn't solved when corner cases are ignored) way. If a language is truely good, it will help programmers, good and bad, to achieve this. If the bad programmer then manages to produce good code, then (s)he is indistinguishable from a good programmer. (The difference between the two then becomes that the good programmer can do this with most problems, while the bad one with only a subset).