This is offensive. Do you want to mean all Clojure developers are garbage? What technology are you working with? Does your entire community consist of stellar i

This is offensive. Do you want to mean all Clojure developers are garbage? What technology are you working with? Does your entire community consist of stellar individuals with no faults? Clojure problems typically start because some member of the team had enough power to convince their manager to do something in Clojure. It is not an organization that typically hires Clojure developers and has already people that know Clojure and can interview Clojure candidates. Clojure projects are typically a byproduct of having developers who are not satisfied with your language (Java most of the time) and try to seek out a better tool for the job. It is not an inherent problem with Clojure or those people. Most developers need an organization to support them and lacking expertise around them they tend to fail in one way or another. Programming Clojure requires huge amount of discipline and guidance with regards to the structure of actual code which you don't have when you just had got hooked up on it and red through couple of articles. Lacking the discipline and guidance, the code reflects thinking process and understanding of Clojure by a single, novice developer who has the most power within the project. But that is because of how powerful and malleable lisp is. Languages like Java force you to use particular solutions to particular problems and have huge amount of public guidance and expectations with regards to program structure which means the code is easier to read and interact with by other developers. You would do better by, instead of being lazy in your thinking and offensive to other communities, to actually try to use your head and try to understand the problem.