I see. So namespaces are helpful here. 
What other team practices do you use? E.g. what do you use for effective 
documentation? With Java you can easily find all helpful operations that 
can be used to manipulate a type. How do you make sure developers find all 
relevant functions in Clojure and don't re-implement old functionality? Not 
that it's a nonexistent problem in the Java world, but Javadoc is very 
helpful there. 

I understand my questions could be directed at most dynamic languages, and 
I'm absolutely not entering the static vs. dynamic debate - but before I 
recommend Clojure for use in a team, I'd like to hear some experiences. 
Another member of this forum has asked about refactoring and was told that 
the problem doesn't arise that often in Clojure. That's good to know. But I 
would like to hear more. I guess that in some organizations the question is 
not "how do I program in a new language", but "how do I develop software in 
a large team using a new language". I've tried to find some online material 
that addresses this issue, but couldn't find any. 

Some languages, such as Erlang, induce a model that is very similar to OO, 
so the development practices, I can assume, are similar. But Clojure is 
completely different. I tried to think back to how we did things in C, but 
there we had header files, that, while annoying, did provide some 
documentation and communicated intents rather well. But in Clojure the 
pieces just seem so... disconnected. It is elegant, but does it provide any 
tools for team communication? Has anyone even encountered such problems at 
all?

And perhaps I shouldn't have used the world "invariably".

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to