Week 26 Recap, BUIDL

Week 26 Recap, BUIDL

By Mike Bivens | Journey to Web3 | 8 Aug 2022


We're making progress towards the level of productivity that I am used to. I was able to work on more than one project this week in between my mountain hikes, beach walks, and driving, which is an improvement from last week.

I'm definitely struggling with an internal battle over not sitting at my desk for 10 to 15 hours a day like I was prior to moving. I haven't taken more than a day off from work or learning web3 in I don't even know how long so I know this road trip is much deserved and needed but the cold turkey switch is not easy.

While it's been nice to be able to get away from it all and reflect, I can't help but feel frustrated at the slow rate my projects are taking because of it. I'll probably get over this and be comfortable just as soon as it's ending and I'm settled back in at my desk and no longer on the road. Until then I'll try to sit still and enjoy the sunsets and corona.

<usual_enterance> If you're new here I'm creating this blog series as I go from coding newbie to working in web3. I'm creating this to reflect on the technical and non-technical growth and to leave it behind for others who might be interested in how they can follow a similar path. </usual_enterance>

In this week's recap:

This Week:

  • Supportive Content
  • Polygon BUIDL IT
  • Road to Web3 Analytics
  • TheDrop
  • WAGMI Squad

Supportive Content

Reading articles and watching videos to learn, review, and research.

The Graph: ‘Google of Blockchains’

The wizard of blockchain

A developer’s guide to Solidity design patterns

FTX CEO and Solana co-founder offer advice for building Web3 ecosystems

Don't wait around for recovery, keep on building, says Web3 exec

Shreyas Hariharan @ Llama || DAO Talk Interviews #5

Scott Moore @ Gitcoin || DAO Talk Interviews #6


Polygon BUIDL IT

I've got version 1 of the NFT marketplace contract up with the supporting JavaScript files. I've modeled this starting draft after Patrick Collin's example in his 32-hour course but as we build the project the files will start to take their own form and become more original work.

The team has started to touch base on this project and re-align on the objective to build a Kickstarter-like NFT marketplace for projects using the ERC1155 standard. While the blockend has taken a strong step forward, the frontend is in need of some strong support. I've got a rough idea of what to build it with but not what to make it look like.

Github Repo


Road to Web3 Analytics

So this one is actually a note about this project's setback. The partner I had found to help me build this has disappeared. We were communicating over Discord and their account was deleted. This was the only way I had to reach out to them and they haven't touched the repo since they were supposed to start the current phase of the project about 15 days ago.

With my partner MIA, I'm choosing to shelve this project but ONLY until I am back from this road trip. I'm very committed to this project and I've got plenty of ideas for what I could do with this project if it's successful. With so many open projects, I have to prioritize and focus on what is time sensitive like the hackathon project (above), and what I have a responsibility to like TheDrop and WAGMI Squad (both below).

Github Repo


TheDrop

My efforts here are more accurately reflected near the top with the <media>. I'm making a special note here for this section though because I'm putting in the effort to move this project forward and thus I believe it should be noted in the recap.

Github Repo


WAGMI Squad

The Squad's update closely resembles TheDrop in that I was mostly focused on trying to get some research done. I've also found myself re-entering conversations and whether we need to be on-chain. We aren't expecting to handle funds so that takes away what I've perceived to be a substantial reason why an organization should be on-chain. On the other hand, having the org on-chain comes with benefits like being able to administer proof-of-membership tokens and very likely, greater recognition as a proper web3 developer community.

Ultimately, I think we will be pursuing an on-chain route and I think we've still got a lot of work ahead of us in pursuing that goal. The core mission of creating a tiny community of growing blockend developers is still sound and we're committed to pursuing it. The best course of action may be to delay the actual development of the DAO and focus on the mission of supporting each other's journeys and contributing to other projects while letting the system design mature.

If you'd like to join this conversation and become a founding member of WAGMI Squad, reach out to me!

Github Repo

Portfolio Website


What's Next?

Heading into next week I have a very brief period of rest before getting busy again so I'm planning on using every minute of that to move forward on some projects and make some progress. I should also have more cell service this week with the region I'm heading to which will allow me to communicate with others more often. Should be a stronger week to work on all the same projects I talked about today (minus the analytics project). 

I also need to work on the action plan over the next couple of weeks for what to tackle in each project, the priority list, and making room the job search. I'm now ready to initiate the real job search and put real focus on it. I've got the list of teams I would love to work with but I'm keeping an eye out for any great opportunity. 


You can find me here:

LinkedIn | GitHub | Twitter |  Portfolio

 

 

 

How do you rate this article?

2


Mike Bivens
Mike Bivens

Blockend Dev | He/Him Founder of WAGMI Squad & TheDrop https://www.msbivens.com/


Journey to Web3
Journey to Web3

I am using this blog to talk about my experiences from pre-software development boot camp towards entering the Web3 ecosystem. I'll share thoughts and what I'm learning, reflect on the journey, and share informational interviews for others to follow along.

Send a $0.01 microtip in crypto to the author, and earn yourself as you read!

20% to author / 80% to me.
We pay the tips from our rewards pool.