3 ms·

Code is not food. You can create a great product with shit code (Or just mediocre code!). Does that make someone a good dev, or a bad dev? How you come to the

Code is not food. You can create a great product with shit code (Or just mediocre code!). Does that make someone a good dev, or a bad dev? How you come to the conclusion he's "just a damn good developer" is a very fair question.

ashtonbaker 4y ago
I think it's actually basically the same. Being a clean, organized cook is probably positively correlated with making good food, but it's not strictly necessary. If someone is writing sloppy code but shipping a project of this overall quality without leaking the "low quality" of their implementation, then I wouldn't presume to call them a "bad dev" - I would probably conclude that they're more efficient than I am at prioritizing where to spend organizational energy.
BiteCode_dev 4y ago
In this analogy, the food is the entire project, and a dev does much more than coding. You can do one thing right with luck, you can't do most things right by luck alone. The guy is fluent in 2 languages, one being known to be hard to master, create a tool that replace several others, get adopted in months by half the community, welcome 172 contributors on a project that is parsing stuff, a hard problem. Also the doc is good. As a professional dev, I never get all those right. Never. So yes, the food is good, and the chef is excellent to get all that stuff right.
cacois 4y ago
Is the function of the developer to write outstanding code, or develop outstanding products? I think there's something to be said for praising the developer that is able to understand user needs so well that they create flawless experiences.
- dev_tty01 4y ago
  >Is the function of the developer to write outstanding code, or develop outstanding products? Just my opinion of course, but to be considered a "damn good developer," you have to do both.
burkaman 4y ago
> You can create a great product with shit code (Or just mediocre code!). Does that make someone a good dev Yes.
deleted 4y ago
[deleted]

ashtonbaker 4y ago

I think it's actually basically the same. Being a clean, organized cook is probably positively correlated with making good food, but it's not strictly necessary. If someone is writing sloppy code but shipping a project of this overall quality without leaking the "low quality" of their implementation, then I wouldn't presume to call them a "bad dev" - I would probably conclude that they're more efficient than I am at prioritizing where to spend organizational energy.

BiteCode_dev 4y ago

In this analogy, the food is the entire project, and a dev does much more than coding. You can do one thing right with luck, you can't do most things right by luck alone. The guy is fluent in 2 languages, one being known to be hard to master, create a tool that replace several others, get adopted in months by half the community, welcome 172 contributors on a project that is parsing stuff, a hard problem. Also the doc is good. As a professional dev, I never get all those right. Never. So yes, the food is good, and the chef is excellent to get all that stuff right.

cacois 4y ago

Is the function of the developer to write outstanding code, or develop outstanding products? I think there's something to be said for praising the developer that is able to understand user needs so well that they create flawless experiences.

dev_tty01 4y ago
>Is the function of the developer to write outstanding code, or develop outstanding products? Just my opinion of course, but to be considered a "damn good developer," you have to do both.

burkaman 4y ago

> You can create a great product with shit code (Or just mediocre code!). Does that make someone a good dev Yes.

deleted 4y ago

[deleted]