Hacker News new | ask | show | jobs
by anonimamente 1422 days ago
Oftentimes we read a comment of the kind "bad or good code can be written in any language or paradigm" in response to writings of the ills or virtues of said language or paradigm. Thus implying that we really shouldn't care of the choice of tools but rather concern ourselves with the individuals using them? This seems like an easy out. Too easy. If it is bad code that we need to worry about, no matter what the syntax or semantics, then how do we do that? Is bad code, like porn, something that we only recognize when we see it, impossible to clearly define? If that's the case, then we really need to figure out some better way to guide us. The mention of Kevlin Henney is particular here in that he has made presentations specifically identifying examples of bad code and how they are made better. If no language or paradigm can help steer us in the right direction--a proposition that I do not believe--then there best be some clear way to tell us how to avoid the pitfalls other than "I know it when I see it."