Seeking Input: Developer Skill Pathways for DotCodeSchool

1

Hey everyone,

I’ve been reflecting on how to make DotCodeSchool more valuable to the community, and came across the idea of creating tailored skill pathways for different developer personas.

What is DotCodeSchool?

DotCodeSchool is an interactive learning platform aimed at helping developers build real-world Web3 apps, specifically within the Polkadot ecosystem. The goal is to make Polkadot development accessible to everyone — from beginners taking their first steps to experienced developers looking to deepen their knowledge.

DotCodeSchool emphasizes hands-on projects and practical applications rather than theoretical concepts alone. We believe that the best way to learn Web3 development is by building and experimenting with real tools and frameworks, just as you would in the field.

Why Skill Pathways?

Polkadot’s ecosystem is diverse and has room for developers from various backgrounds — each with unique skills, motivations, and learning preferences. Right now, the challenge is to provide structured, engaging guidance that meets the needs of each type of developer. Platforms like Codecademy use skill-specific pathways to increase engagement and success rates because they make learning feel relevant and progressively rewarding (progressive overload).

By creating dedicated learning paths for each developer type, we can leverage their existing skills while gradually introducing more complex concepts specific to Polkadot. I think this will make the onboarding process is smoother, more relevant, and ultimately more successful.

The Six Developer Personas

To make DotCodeSchool truly valuable, we need to recognize that not all developers are the same. Polkadot’s ecosystem attracts a diverse range of developers, each bringing unique skills, motivations, and goals. To create effective learning paths, I’m focusing on these six key personas:

  1. Frontend Developers: Focus on building interactive dApps with wallet integration and real-time data.
  2. Backend Developers: Create APIs and data services that interact with blockchain data.
  3. DevOps Engineers: Run and maintain nodes, ensure network reliability, automate updates and build monitoring systems.
  4. Smart Contract Developers: Build decentralized apps and services on Plaza or using Ink!.
  5. Core Blockchain Developers (Runtime, Pallets, Nodes): Develop custom pallets and parachain runtimes.
  6. Data Analysts and Indexers: Extract and analyze on-chain data for insights and dashboards.

Why Personalizing These Paths Matters:

By understanding each persona’s skills, motivations, and needs, we can make learning experiences that resonate, keep them engaged, and make the journey rewarding at every step. Instead of generic tutorials, we can offer progressive, hands-on projects that help them build real, “show-offable” applications on Polkadot.

This structured approach not only helps newcomers get started but also ensures that as they progress, they see clear, tangible growth in their skills — keeping them hooked on building with Web3 tech.

What I Mean by Skill Pathways:

image
image903×816 118 KB

When I say “skill pathways,” I’m not talking about building new tech features or complicated onboarding flows. I’m talking about writing well-crafted, carefully curated content that caters specifically to each developer type.

Focusing on making the learning process rewarding and practical by offering:

  • Quick wins: Low-commitment, instantly gratifying mini-projects (30min-1h).
  • Step-Up Challenges: Building on small successes to boost confidence (within a day or two).
  • Project Sprints: Practical applications to solidify concepts (1-2 weeks).
  • Advanced Exploration: Delving deeper into ecosystem-specific skills (time commitment here will vary based on user-specific interest).
  • Mastery Projects: Real-world, portfolio-ready applications (4-6 weeks).
  • Community Contribution: Encouraging learners to share their projects and insights (buildondot.com to list community vetted ideas, ecosystem bounties, polkadot-sdk issues, etc. for students to work on).

Request For Your Input:

I’d love your feedback on this idea to ensure we’re moving in the right direction. So here are my questions to you:

  • Does this approach make sense to you?
  • Do you think it will be valuable to the community?
  • Which top three pathways should I focus on first, and in what order?
  • Would you like to contribute or share your own learning experiences?

PS - I’d also like to make an open call for community contributions.

DotCodeSchool is fully open-source, and we’ve recently revamped our publishing system to support MDX tutorials and articles. You can now include interactive features like quizzes, making it easier than ever to contribute content and make learning engaging. Here’s a quick video demonstrating just how easy it is now:

https://x.com/i/status/1920064594082742526

If you’re interested in contributing in any way to this effort, I would love to hear from you. Your contributions can help shape the future of how developers learn and build on Polkadot and they will directly shape the direction of DotCodeSchool.

If this speaks to you, please do reach out to me directly on Telegram: Contact @batmancodes

8 Likes
2

Hi @batman,

This approach makes 101% sense to me! :raising_hands:

I truly believe this will be incredibly valuable to the community — speaking from personal experience, I remember when I first tried to integrate a wallet connect feature into my dApp. It took me 2–3 hours just to find the right approach. If DotCodeSchool had a tutorial for that back then, it would’ve saved me so much time — so for newcomers, having guided pathways like this would be a game-changer.

In terms of prioritization, I’d suggest starting with:

  1. Frontend Developers – since many newcomers are eager to get something visual working quickly.
  2. Backend Developers – to complement the frontend and teach how to handle blockchain data.
  3. Smart Contract Developers – because once people are comfortable with dApps, they naturally want to explore the logic behind them.

And yes, I’d love to contribute! I’m excited to help make DotCodeSchool the go-to place for newcomers to the Polkadot ecosystem.

Let me know how I can help :raising_hands:

3

If you wish to contribute, I think you could start with the problem you described here:

Perhaps you could write an article/short course teaching newcomers how to do this?

You can use this to get started: frontend/content at master · dotcodeschool/frontend · GitHub

Feel free to reach out to me if any of the contribution guidelines/processes to be unclear, buggy or difficult.

4

Glad to see dotcodeschool advancing, becoming more open and helping developers get into the ecosystem in a structured way.

I love the idea of skill pathways. We have so many ways to develop on polkadot, even the papermoon docs clearly separate paths like parachains and smart contracts.
I love that we’re adding frontend to the mix, to showcase how building good interfaces with our tools can be easy and help more people create those.

While I do find some developer personas like devops to be very interesting, I would prioritize frontend and smart contracts as those are the things we expect to see a lot of in the Hub.

I’d also love to contribute! Keep up the good work

2 Likes
5

Thank you for your support @francisco.aguirre! I tend to agree that frontend seems to be the best starting point based on the feedback so far. It’s clear that focusing on quick-win projects and gradually scaling to more complex ones is the way to go.

So, the plan from here is to move fast and iterate later. I’d rather have an imperfect path that we can refine based on real feedback than spend too long planning upfront.

Next Steps:

  1. I’ll come up with a set of specific frontend tutorials, starting with small, practical projects that can be completed quickly.
  2. Once I have a draft of the frontend skill path, I’ll share the overview here on this forum post to gather feedback before finalizing.
  3. Based on the feedback, I’ll refine the path and move forward with creating and publishing the tutorials.

I really appreciate your willingness to contribute! Let me know if you have any ideas on how we could make it easier or more appealing for yourself (or anyone else) to get involved. Your input would be super valuable, whether it’s about content ideas or improving the contribution process.

Also, whenever you have time, I’d love to hear your feedback on the tutorials as they come out.

Please don’t hesitate to reach out to me if you run into any hiccups when publishing a tutorial or have any suggestions along the way.

6

Great work on DotCodeSchool @batman ! Yeah i agree with the others, these paths type would make a lot of sense, with a focus on creating real applications and not just simple exercises, thats how you really learn something !

1 Like