How the hell do you want us to do a

pact hackathon when we have like 10 pact developers?

If it wants to reach more developers, Kadena should create strong funds for developers.

Disagree

Have you ever heard of Dappstaking?

Offering bigger prizes for the hackathon can really make a difference. Imagine this: instead of the usual $50k grants, we go big. This would get people excited about learning to code in Pact, realizing there's much to gain with Kadena's tech. It's not just about the money; it's about what coding on such an advanced platform can lead to. We're talking major innovations in VR, AI, gaming on Web 3.0, and more. With substantial rewards, we can attract the best talent, sparking real interest and pushing the boundaries of what's possible on Kadena. This is how we can showcase Kadena's capabilities and ensure it's recognized for its technological feats.

No, it doesn’t work that way. You’re putting the cart before the horse. Devs want documentation, which we’re rebuilding. They want MVC, which we’re building

I understand your perspective. Making a simple post on both your personal Twitter and Kadena's official account with a form detailing the hackathon could indeed gauge interest and identify developers willing and capable of learning and developing on Pact. There are undoubtedly self-taught talents and geniuses out there who, given the right challenge and competition, would be eager to dive into Pact development. This approach not only tests the waters for potential participation but also promotes self-learning and innovation within the Kadena ecosystem. Engaging directly with the community this way can highlight the demand for documentation and MVCs you're working on,

Billy Mike is doing a good job man, let him build the education tools first bud.

Of course, Mike is doing a great job, but if other projects are outperforming us in terms of development, we need to innovate to do better. That's why I proposed a solution that most seem to agree with, and I don't see what's so complicated about creating a form and running some ads to test whether it can work or not.

Look, what they are doing is really difficult. But some things could have been done before Mike. It is late, but there is still progress.

you would finish the hackathon and half the devs wouldn't have pact running correctly on their machines we need better documentation, friendlier ways for people to start using pact imo, the current tutorials do not help you get started. they highlight some great unique features of pact, but are very frustrating for someone who is starting out If I was doing them, I would start by doing a walkthrough on how to get pact running on mac/linux/pc only then would I begin going into pact and there needs to be better access to documentation, its hidden somewhere in the website. You need to google "pact documentation" and have the first or second link be the full language documentation. So yeah, before any hackathon, these need to be addressed in my opinion

Thank you for your message. Well then, we need to recruit someone who knows how to develop on Pact and have them work for 2 months on a training program that includes all the necessary information to create on Pact. I don't see what's so hard about settin

And you propose this training in 2 months, at the same time as the hackathon. It sounds simple when said like that, but it's totally feasible. A good developer on Pact can create a 20-hour training program with solid modules on Pact that will help developers who are quite experienced in other languages to understand Pact well (the basis of coding is just understanding at first; once understood, practice, which is 90% of learning, takes place).

its not just tutorials, its the whole design of the documentation and learning tools the things is kadena had a big project for this, but for some reason it was dropped

As community members we have the right to throw out ideas to other community members. Get the community members engaged in your ideas. Team members are here all the time but they have a life too. We should let Team members engage when they feel the need to do so.