I always say, just remember that there are 3 presentations, the one you prepare, the one you give and the one you wanted to give. You will forget to say things, you will add things and afterwards you will suddenly realise things you should have said. All those things will happen. So don't worry too much about what you actually say in the presentation. just my 2 c.

Awesome. I taught a function programming module using clojure on an undergrad uni course a few years ago. I think that I found it best to stay engaged with the people listening and trying to answer their questions. They all had different expectations as to what the process of programming was like and introducing them to REPL driven development challenged different people's assumptions in different ways. Two way interaction was key to getting past that. A workshop focused on a specific codebase sounds like a good forum to help with that 😉 Good luck.

Amazing, you'll be great 💪

I feel like getting them to write actual code as soon as is practicable is maybe a good idea.

one day is not a long period of time.

Learning is in the fingers

I don’t think I can hope to help them learn very much Clojure during just a day. My assignment is actually to inject some enthusiasm into the prospect of them taking responsibility for the Clojure+ClojureScript app in question. And to get them started with that. About the enthusiasm part…. my customer also wants me to inject some enthusiasm for Clojure to a broader audience, so the day will start with a presentation and some demos of interactive programming. Then workshop for the team. and that will have them learning via their fingers for the rest of the day, I have just decided 😃. (Which is also shorter than a full day, I just learnt.)

It certainly is a short amount of time. I did a looooot of fumbling around when I first learned Clojure on my own. Without dot completion as I knew it from Java, it's hard to know which function to call and really get started. A mentor would have helped immensely, but you can't sit on everyone's shoulder. I would maybe think about a very restricted domain for them to work with, naming some pertinent functions in advance. But I've never done this sort of thing, only 1-1 mentoring, so idk what works best. Maybe they're all superstars and will figure everything out 🙂

Fantastic! Congrats @U0ETXRFEW

Go you 💪 💪 💪

If you're just looking to get the name from a symbol without quoting it, you could do something like

(defmacro var-name-str [expr]
  (name expr))

(defn var-name-str2 [v]
  (name (.toSymbol v))) 

that is much better as it avoids a macro

and the first rule of macro club is...

the things I'm dealing with atm are vars I've set up with (def

I think macro's are fine if you want to control the syntax, but if you're ok with quoting things in your code or wrapping them in functions to pass around, then you very rarely need them. And the advantage of var quoting them will be less typos. The macro will swallow errors if the var doesn't exist.

I only really want a macro if there is no other way around it.

this function looks perfect to me

thanks!