Ethereum React Native Boilerplate

Purpose

Forked this boilerplate thinking I was going to do development work with the Magic Mushroom Clubhouse NFT community. I connected with a couple of devs, but never built deep working relationships. The conversations seemed to orbit around how we could profit rather than what we could build. I accepted money and never really delivered anything spectacular. That is the honest truth.

Stack

What I Learned

• There is a difference between being in a space and being ready for a space. At this point in my career, I had the bootcamp, an apprenticeship, and a stint as the lead coder at Salotto (a billiards company) — where my progress had slowed so much that they let me go. I was two years into coding. My skills were not where they are now. The ambition outpaced the ability, and that gap showed up in what I delivered.
• Accepting money for work you do not deliver is a lesson that only needs to happen once. I am not proud of it. I did not set out to underdeliver — the scope was unclear, the relationships were shallow, and my technical capacity was not where the project needed it to be. The experience taught me to be honest about what I can deliver before I commit, not after.
• Community management in NFT projects was genuinely impressive work. The Magic Mushroom Clubhouse team ran Discords with thousands of members, coordinated drops, managed expectations, handled rug pull fears, moderated 24/7, and kept energy high through market downturns. That is operational work at a level most people do not appreciate. Whether or not the underlying asset had lasting value, the community management was real skill.
• The relationship dynamic in crypto freelance work often defaults to "how do we profit" rather than "what are we building." This is not unique to crypto — it happens in any gold rush. But it makes it hard to form the kind of deep working relationships where great products get built. The best collaborations I have had since were rooted in shared vision, not shared upside.

Key Insights

• This was the low point of the timeline — and it needed to be. Being let go from Salotto because my progress stalled. Accepting work I could not deliver in the NFT space. Dabbling in projects without the depth to finish them. From the outside, this looks like a string of failures. From the inside, it was a season of learning compressed into the most uncomfortable possible format.
• The failures in this period were not random — they were diagnostic. Getting let go from Salotto told me I needed to level up my fundamentals, not just chase new frameworks. Underdelivering in the NFT space told me I needed to be honest about my capabilities before taking on commitments. Not building deep dev relationships told me that collaboration requires more than shared financial incentive. Each failure pointed at a specific weakness.
• I want to be careful not to speak badly of anyone in this space. The people I worked with were hustling, building communities, and taking real risks. I respect and admire the intensity of their operations. The fact that I did not thrive in that environment says more about where I was in my development than about the quality of their work.
• Two years in, having dove in and failed repeatedly, the learning was tremendous. The boilerplate repos, the crypto experiments, the unfinished projects, the job that ended — all of it was raw material. The developer who emerged from this period was not the same one who entered it. The skills were sharper, the self-awareness was deeper, and the hustle was tempered by honesty about what I could and could not do. That honesty is the actual foundation. Not the code.