And did you ever systematically practice Literate Programming approach?
Yes and like I've said elsewhere, I'm not entirely sure you've understood the concept you are trying to teach me. "Code within comments" isn't what you are preaching right now.
"Code within comments" isn't what you are preaching right now.
Why? That's exactly the approach I'm talking about. You write down the story, meticulously, and you illustrate the story with a code that implements it. Not the other way around.
I can tell you exactly 0 programmers I've met in my life who when given the instruction...
write down the story, meticulously
...would not quit or skim the documentation part, leaving you with mismatched, unverifiable rubbish all around your code. I can think of no way to keep that documentation up to date or to verify that the code and the comments do the same thing.
Looks like you always worked with some truly awful programmers.
My criteria for a good programmer is not any technical competency, not some arcane CS knowledge, etc. The best programmers I met are good writers.
Once again, you cannot keep documentation up to date. Only if your code and your documentation are the same they can be kept in sync. Then any pull request is trivial to verify - you see all the documentation context right in front of you, and if the code change proposed is going against what is said in the text, it's obvious immediately.
Well, point is we disagree at a very fundamental level. I asked about comments in how people code, your complaint was that everyone but you does it wrong, called Uncle Bob a "buffoon" and everyone I've ever worked with for 20 years a "truly awful programmer".
So keep preaching, nobody is jumping on such a bitter train.
your complaint was that everyone but you does it wrong
Lol. Do you have any idea of how many people are using, say, Jupyter notebooks?
called Uncle Bob a "buffoon"
And I'm not alone. Any sane person looks at uncle bob with nothing more than a plain disgust.
and everyone I've ever worked with for 20 years a "truly awful programmer"
Again, it happens in certain industries. Good programmers try to stay away from such places. Birds of feather, and so on.
And yes, I have a very good reason to believe that anyone who takes uncle bob bullshit seriously is lost forever, and I'd do whatever I can to never work with such toxic, destructive people.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
And did you ever systematically practice Literate Programming approach? It works much better than any of the "clean code" madness.
There is simply no such a thing as an expressive design. Any design is still missing all of the background train of thought that lead to it.
Yes and like I've said elsewhere, I'm not entirely sure you've understood the concept you are trying to teach me. "Code within comments" isn't what you are preaching right now.
Why? That's exactly the approach I'm talking about. You write down the story, meticulously, and you illustrate the story with a code that implements it. Not the other way around.
I can tell you exactly 0 programmers I've met in my life who when given the instruction...
...would not quit or skim the documentation part, leaving you with mismatched, unverifiable rubbish all around your code. I can think of no way to keep that documentation up to date or to verify that the code and the comments do the same thing.
Looks like you always worked with some truly awful programmers.
My criteria for a good programmer is not any technical competency, not some arcane CS knowledge, etc. The best programmers I met are good writers.
Once again, you cannot keep documentation up to date. Only if your code and your documentation are the same they can be kept in sync. Then any pull request is trivial to verify - you see all the documentation context right in front of you, and if the code change proposed is going against what is said in the text, it's obvious immediately.
Well, point is we disagree at a very fundamental level. I asked about comments in how people code, your complaint was that everyone but you does it wrong, called Uncle Bob a "buffoon" and everyone I've ever worked with for 20 years a "truly awful programmer".
So keep preaching, nobody is jumping on such a bitter train.
Lol. Do you have any idea of how many people are using, say, Jupyter notebooks?
And I'm not alone. Any sane person looks at uncle bob with nothing more than a plain disgust.
Again, it happens in certain industries. Good programmers try to stay away from such places. Birds of feather, and so on.
And yes, I have a very good reason to believe that anyone who takes uncle bob bullshit seriously is lost forever, and I'd do whatever I can to never work with such toxic, destructive people.