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.
How you come to the conclusion he's "just a damn good developer" is a very fair question.
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.
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.
Just my opinion of course, but to be considered a "damn good developer," you have to do both.
Yes.