I think the issue with large programs is not the language but software engineering. A large program should be well designed and architected, and this is a problem (I think) many people in clojure and functional programming in general have. "Clojure is a very high level and concise language so I'll grow my program as I type". I'm not proposing UML or any specific tool or technique, but analysis and design are a important part of a large software. It's easier to understand your problem if you look at your high level documentation/diagrams than look at code. Of course some problems and refactor will happen no matter how well you designed, but you'll understand better what you did and what you should do.
Islon On Jul 4, 9:40 am, James Keats <james.w.ke...@gmail.com> wrote: > On Jul 4, 1:26 pm, James Keats <james.w.ke...@gmail.com> wrote: > > > On Jul 4, 5:45 am, Christian Schuhegger > > A good > > book to get you started would SEMANTIC WEB for the WORKING ONTOLOGIST, > > of which a second edition has recently come out. :-) > > Sorry about the unintentional "to get you started" figure of speech; I > note you said you already had rdf/owl in your kit. It's not out of > underestimating your knowledge (though it might be out of my sense of > being mildly overwhelmed by the still remaining reading list I already > have of semantic web books, Springer just keeps dropping them like > rain. :-) -- 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
