Polkadot - Feedback and local tweaks from UCB run-of-show incoperated

[nuke-web3]

Please take notes as you have them here from students and from your perspective 🙏

What was good, bad, ugly? Any lessons learned?

Also - [ ] items of things that need a FIXME for next time to close this issue out we know of.

TODO before we close out the UCB cohort & tag the content repo

• Add a few things here...

[Sophia-Gold]

I was mostly pretty happy with it and just have two points of criticism:

• In future iterations, we can't afford to have this drain anywhere near the amount of time it did from engineers on Parachains Core. I think the time spent on actual content creation was manageable and most of it was on organizing and scheduling. I'd like someone from PBA to take ownership of this in the future and also have the schedule more or less set in stone around the time we're doing dry runs. I think you'll find it's much easier to get buy in from engineers when someone else is in charge of the schedule and structure and it's crystal clear from the beginning.
• The placement of the Polkadot module inside the curriculum was a bit odd to me (probably true for XCM as well). Engineers don't actually need to know this stuff in order to be effective contributors in the ecosystem or even core engineers in many parts of the stack, so I understand having it at the end while they were working on FRAME assignments with that in mind. But I couldn't help feeling it should have been showcased more. I think the way to do this is target it more at the founders track. They should be able to communicate the value Polkadot's design adds to their applications.

[shawntabrizi]

I think the way to do this is target it more at the founders track.

Small disagree here. I think this would totally go over their heads based on the cohort we had this time around.

At least some of the students in the engineering track really understood what you were presenting, and I think others will appreciate it as their blockchain career develops.