Why We’re Shipping Curriculum Before It’s “Done” (And Why You Should Too)

At Midnight, we’re building a new kind of blockchain. One focused on data protection, developer experience, and real-world impact.

And as we grow our developer ecosystem, we’re doing something many teams are afraid to do.

We’re releasing our developer curriculum before it’s “done.”

Not because we’re lazy.

Because we believe that early feedback, real-world usage, and community collaboration will lead us to a stronger, more usable learning experience.

The Trap of Waiting for Perfect

Too many developer education teams hold back content until it’s “finished.” Polished. Market-ready.

But the truth is, good curriculum is never truly finished.

As someone who’s been both a high school English teacher and a DevRel leader, I’ve seen firsthand that the best learning doesn’t come from a perfect script. It comes from iteration. From shipping. From engaging with students/learners while the material is still taking shape.

So we’re taking a different approach.

We're shipping early and learning in the open. We're publishing usable content early, inviting feedback, and improving it alongside the developers who use it.

Introducing the Midnight Developer Academy

Recently, we quietly launched Midnight Developer Academy: our educational hub for developers who want to become experts in Zero-Knowledge Proofs and learn how to build DApps with data protection at the core.

Here’s what’s live now:

• 👩‍🎓 The first 3 of 8 core modules
• ✍️ Written, direct, and focused on hands-on learning
• ⚡ Designed for usability, not perfection

And here’s what’s on the roadmap/coming soon:

• 🎥 Video content and interactive labs
• 🌍 University partnerships and blockchain society integrations
• 💻 Self-paced learning on major online platforms
• 🧑‍🏫 Cohort-based workshops and live office hours
• 🤝 Partner-contributed modules on advanced use cases

This isn’t about checking a box. It’s about delivering real value now and letting our developers help shape what comes next.

Why I Love This Approach

By shipping early, we’re already seeing wins:

• Developers are completing the first modules and asking for more
• We’re collecting specific, actionable feedback to guide the next releases
• Our community feels involved, not sidelined

This is our bet:

1. Progress beats perfection
2. Trust is built through transparency
3. Gatekeeping (is toxic and) slows learning

If you’re in DevRel, developer education, documentation, or product enablement, ask yourself:

👉 What’s the cost of waiting until it’s “done”?

👉 What opportunities are you missing while you polish?

👉 Could your community be helping you right now?

Build With, Not Just For

We believe that building with developers, not just for them, is how ecosystems thrive.

That means opening the door earlier. Listening harder. And iterating out in the open.

So here’s our call to action to the Midnight community:

💥 Dive into the first three modules

📝 Tell us what’s missing

📣 Help shape what comes next

We’re not waiting for perfect.

We’re learning, shipping, and growing together!