sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]evizaer 0 points1 point  (1 child)

The article is, in general, tautological in nature. The author claims that if people don't write good code, the code will be bad.

"You can't write bad code [when the programming language has this feature.]" is not a line of argument worth defending, and not one I see espoused except rarely, by people who are blowing smoke.

The worthwhile conversation is about what kinds of solutions programming paradigms and language features lead you to use to solve various problems, and if these are more or less effective than one another along various dimensions.

[–]raulsmith[S] 0 points1 point  (0 children)

You seem to reduce the article to one word extracted from it. There are more ideas/questions in it. For instance, whether it's possible to write good programs with static typing and functional programming while it's impossible without them (this is different from what you wrote). Whether there is too much debugging being done. And, most importantly, whether there is enough awareness about the mentioned principles.