-
@Wright2Tweet Yes! Some of this might be opinions, not fact. 1. Build in time for breaks, and more time than you think. Not sure how long yours is, but 4 hours is a long time. I built in a break at 2 hours in. That wasn't enough. We ended up taking 2, at about 1.5 hours and 3 hours.Permalink On twitter.com
Mood +1 🙂
-
@Wright2Tweet 2. The breaks were longer than I wanted, too. Some people will keep working when it's break time, and then take their break 2 minutes before you want to start up again. I'm not sure how to deal with this, yet. If you come up with something, let me know!Permalink On twitter.com
Mood +1 🙂
-
@Wright2Tweet 3. People won't move very quickly. I knew this going in, I built a *TON* of work for the exercises, purposely so that no one would finish. I think some were disappointed/frustrated in how far they didn't get, though. 4. Be very very very clear in your instructions. Very clear.Permalink On twitter.com
Mood -3 🙁
-
@Wright2Tweet 5. Figure out what kind of workshop you want to be. Some are lots of talking. Some are heads-down coding for 4 hours. I like alternating talking with exercises. 10 minutes of introducing concepts, followed by 30 minutes of working, followed by 5 minutes of recap - that's my jam.Permalink On twitter.com
Mood +5 🙂
-
@Wright2Tweet 6. It's a lot of effort to prepare. A 1-hour talk takes me about 40 hours to prepare; my 4 hour TDD workshop took me at least 80 hours. Probably 2/3 of it was on exercises, 1/3 on slides. I didn't put a lot of effort into making kickass slides.On twitter.com
Mood 0
-
@Wright2Tweet Hope that helps! It was fun, & I'm hoping I can give this workshop again. Actually, I hope workshops is my full-time job in the kind-of-near future. I feel like I was able to give way more real-life experience to people than I could ever do in one hour. 10/10 would do again.Permalink On twitter.com
❤️ 2 Favorites
Mood +14 🙂