Training tip: how to review a layered architecture

I'm in India, giving a training to a class of young developers. The focus is coding under a given proprietary framework and architecture, most of which I designed when working in Amdocs.

I find it in many frameworks and systems: there's a layered approach with components interacting with each other. I found a great way to review the entire architecture and flow.

I handed each of the students a note, with a type of component (or a given generic component like a helper or factory). In turn, they formed a row, each according to his/her order in the process. They explained what they were doing, how and who are they calling next. Of course, if any of them got stuck with the answers I quickly opened it up for the whole class. It's important to keep the interaction flowing.

It was a fun way for reviewing the material. I spiced it with some humor and it was a very pleasant exercise. I'm sure they will remember it. It took about 45 minutes and nobody got tired or bored, although it was all just reviewing the material they knew. Plus, it makes everybody participate, even those who usually don't, and without being too intimidating (like a test).

Comments

[Neha]

Hi Zviki,
The moment you left the class i looked this up...
I was a part of this class you have mentioned(n i was the service in this exercise).. n trust me we all will remember that indeed...
It was great having you as a trainer. You are THE BEST...

Loads of luck,
Neha Bhagurkar

[Zviki]

Thanks, Neha, for the kind words.
You all were great students and I enjoyed working with you for the passing two weeks.

I wish you all the best in your professional career.

Zviki