Only one link: http://www.4clojure.com/
That's what we did a few month ago when we did an introduction to Clojure
for our fellow co-workers.
It worked well, to the point that it crashed www.4clojure.com :)
But on Clojure IRC, Anthony Grimes (IORayne) was kind to reboot the server,
it demonstrate
On Dec 21, 2012, at 2:27 PM, ulsa wrote:
> I used an early version of Clooj in a workshop some time ago, but got burned
> by some bug that rendered the REPL crazy and shredding people's code. That
> scared me away. Probably much better now, though.
I've taught a couple of courses using clooj an
This is good advice. I think you can cover a lot of ground using this
approach, which I guess you need to do when writing a book.
As I mentioned in another post, I believe I have to choose between covering
a lot of ground and building them a foundation that they can experiment on
further.
On
I also suspect that the IDE is important. These guys are experienced
people, and I think that once they have an environment that works and they
have some control over, they will have a foundation. I think they need and
want to know how namespaces work, so that they can see how to modularize
cod
I have used the isBlank example in presentations. It's not a bad starting
point. Might look at how it could be used in a workshop. Thanks.
On Thursday, 20 December 2012 17:16:19 UTC+1, Thomas wrote:
>
> If you need to touch on the why of Clojure I found the example in the
> beginning Stuart Hall
I used an early version of Clooj in a workshop some time ago, but got
burned by some bug that rendered the REPL crazy and shredding people's
code. That scared me away. Probably much better now, though.
On Wednesday, 19 December 2012 20:38:05 UTC+1, Nando Breiter wrote:
>
> What about Clooj?
> h
On Dec 20, 2012, at 8:55 PM, Seth Chandler wrote:
> but in dealing with file locations, dependency management, projects,
> Leiningen, all of which are -- with due respect -- very difficult,
> particularly for people not coming from an Eclipse or similar background.
In my book, I decided to ha
I would spend A LOT of time on working with the IDE be it
Eclipse/Counterclockwise, IntelliJ or whatever. In my limited experience
the main impediment to Clojure is not Clojure itself, which is very
sensible, but in dealing with file locations, dependency management,
projects, Leiningen, all o
If you need to touch on the why of Clojure I found the example in the
beginning Stuart Halloways book quite a good one. the isBlank in Java and
the one line blank? equivalent in Clojure. Show them the Java, talk it
through with them and then highlight some of its downsides (multiple if
statemen
What about Clooj?
http://dev.clojure.org/display/doc/getting+started+with+Clooj
Is it too buggy, or lacking in features, to start out with?
On Tue, Dec 18, 2012 at 11:27 AM, ulsa wrote:
> Good point.
>
> I really would like themselves to be able to set up their own environment.
> I think it giv
Good point.
I really would like themselves to be able to set up their own environment.
I think it gives them a sense of control. However, as a fallback, it would
be great with a virtual machine with everything working. I'll consider that.
I believe you can get a similar level of interactivity
1. install Leiningen and learn the basics
2. get everyone an editing environment, with the option of using either
Emacs, IntelliJ, or Eclipse
I would have people do this in advance, or provide a canned environment
that has a better chance of "just working". There's decent odds that these
two steps
> I think, however, that there is a risk of a disconnect, where newcomers
> don't really grasp that there is a JVM running and that code is actually
> compiled and injected into it, and that it's for real. They are used to
> mickey mouse interactive tools that don't provide the real thing, and
Interesting idea. Let me ponder that.
When one starts pulling on a thread like metadata for example, all kinds of
interesting facets pop up. That's what I meant with my comment about the XP
practices graph thing. Different Clojure capabilities support and enable
other capabilities, and you need
Thanks, I won't forget the REPL.
I think, however, that there is a risk of a disconnect, where newcomers
don't really grasp that there is a JVM running and that code is actually
compiled and injected into it, and that it's for real. They are used to
mickey mouse interactive tools that don't pr
I think showing people how metadata works usually makes people start dreaming,
and exposes them to docstrings and arglists which I think is crucial to
self-directed learning.
So, I think I'd show them: (doc ...), and then show how that is metadata, and
for quicker folks you could show how to ad
> My plan was to do something like this:
>
> *First half of the day*
>
> 1. install Leiningen and learn the basics
> 2. get everyone an editing environment, with the option of using either
> Emacs, IntelliJ, or Eclipse
> 3. teach the basics and let everyone follow along in their own environment
Good points, thanks.
It's so easy to overload them, because one wants to teach them every little
piece of gold that's in there. I think it was in one of the old XP books,
where there was this graph that showed which practices were supported by or
enabled other practices. I would love to see so
There is one advice I can give from my teaching experience: don't overwhelm
them with data. A person can assimilate only so many concepts in a day, no
matter whether the workshop lasts two or eight hours.
Pick a few key concepts and spend much time on approaching each concept
from many differe
In a couple of months, I'll have a whole day of teaching Clojure to ten of
my colleagues. They are experienced Java programmers, but otherwise Clojure
rookies. Any tips on how to structure such a workshop day?
--
You received this message because you are subscribed to the Google
Groups "Clojure
20 matches
Mail list logo
