We had a great event at the council the other day about Developer Education. We all agreed that open sourcing some information around types of lessons, timing, lesson plans, etc. would help us all do better in keeping up to date with new information, as well as improve the quality of our offerings to our students.
I was wondering if anyone had the notes from that sub-ring gathering?
(kambala ethereum)
blockchain academy
Zastrin
b9labs
Kommerce
Sections:
Dev education
ux
newcomers
decentralised concepts
funding/grants infrastructure
Topics:
empowering
up to date repos of info (curating)
newcomers
general onboarding
foss
DEV EDUCATION SUB-RING
Outcomes:
Lots of resources, finding the resources.
Curation
Sharing Experiences with resources, flagging incorrect/outdated resources
Technology moving so fast.
Feedback mechanism on content.
Developer hard to find time to share education resources.
Evolution intimidating for end learners. Information overload.
Distill core concepts. Concepts evolve/iterative.
Sharing workshop results. Order and format of content.
Good examples.
Wrap content around blockchain concepts, but suspend toxic semantics.
Resource, beyond remix.
Remix first, broader concepts.
Formats:
“Code-together” format.
16hr session - mob programming: 1 on keyboard, near circle guiding (documentation, theory), the rest watching and occasional points. Instructor takes back-seat, only format feedback, or.
first day: basics, last hour: ticket app idea. Forms template for day 2.
Modular ideas. Smart contract + dapp + ticket payment, …
private network in class for speed, but real testnets more realistic.
1hr non-tech
online videos
Resources:
Consensys academy
gas analogy - car petrol, internet cafe
Solidity, but also consider entire stack, web3, … (duration 2hrs-…)
teaching of frameworks/dev-tools: truffle, python (pyevm)
Format: markdown, latex…
licenses / unbranded (neutral)
git attribution
Application:
examples
product concept voted by group eg micro-loans, food processing, auction, …