Had a shakeup in my travel plans this week that allowed for extra time to coordinate with others and focus on the work relevant to this blog. Took a load of stress off my shoulders but it will impact next week's plans.
I had enough downtime this week between the road trips to also set up my workstation and actually use it which was seriously refreshing. Programming from a single-screen laptop has not been ideal but it's been enough over the last few weeks. I'm still dealing with the same struggles though that I've talked about over the last few weeks. The end of these road trips is quickly approaching through, it's bittersweet to say the least.
I've realized that it's not always clear what I've learned over the week when I report in these recaps. I think I do a good job providing an overview of what I'm working on and what I have to do in each but not necessarily what concepts that I'm actually learning or improving. So I'll try to do that here in the intro more explicitly going forward (although I'm hoping there won't be too many weeks left doing this).
So here's what I've been learning this week;
- Making multiple API calls with one click
- Understanding DAO governance models
- Using the Alchemy SDK
- Reviewing DeFi concepts
<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
- TheDrop
- WAGMI Squad
- Road to Web3 Analytics
- Job Search
Supportive Content
Reading articles and watching videos to learn, review, and research.
Reflections on the DAO movement - Ameen Soleimani and Alex Napheys
Decentralized Governance. How to Put Power Into the Hands of the People
What the future of web3 means for credentials
I Want To Explain DeFi To My Dad
How to Get Into Crypto and Web3 as a Developer
Airdrop culture could pose integral threat to DeFi industry
DeFi Money Legos and Composability | Chainlink Tech Talk #6
Polygon BUIDL IT
This week, I built out some issues on Github to help with development and checked in with the team to talk through what needed to be done like the contract factory for users to call when they are creating new projects on the dApp.
I also looked around for some ideas on how to design the front-end, so that will come this next week. I'll also be including TheGraph for indexing the activity by the users.
TheDrop
No new coding here. With Alchemy's SDK update I'm planning on changing course with this and switching over to that instead of rebuilding with it later like I was originally planning. The SDK is much easier to use now and while it's a brief backtrack, it'll be so worth it.
WAGMI Squad
The squad agreed on postponing the coding of the DAO and instead, focus on the goals of the organization while more research can be done on how we should build it.
Road to Web3 Analytics
Sike, I said last week this was getting postponed until later down the line but the partner I thought went MIA showed back up. With him back in the game, we started working away on this. I updated the API call to make it a single line instead of breaking it up. This looked cleaner and because this project is only looking to pull data on one project, it doesn't need to take input variables.
Additionally, with Road to Web3's release of their student pass, we decided to change the design. Previously, we were planning to run the API call on each of the 10 PoK tokens to pull in the holders addresses, removing the duplicates, and then checking those wallets histories. Instead, we are going to run the API call on just the student pass and check the wallet history of those wallets. This is a much easier strategy and removes the step of excluding any duplicates.
I'm also starting to assess how to reconfigure this tool for use in TheDrop after it's been developed.
Job Search
This week I freshened up my materials by updating my personal website to reflect some newer projects and changed my resume style to bring it in line with some recommendations I've received from others in web3 jobs. Hopefully we'll see this pay off, there's some other supplemental materials I would like to create (like a LinkedIn about video) but I'll have to get to those later on when I have more time.
What's Next?
Next week will be the last travel week! I'll keep up on what I can, when I can, but we're going high up in the Rocky Mountains for hiking so I'm expecting very little internet opportunity. This next week, I'm looking to review and dive deeper into smart contract security. The "supportive content" will mostly feature this effort. In addition, the coding goals are to iterate the Road to Web3 API call to collect the additional addresses the API endpoint's limit impedes. After these items, I'll be focusing on identifying and applying for employment opportunities.
The stretch goal is to work on the front end for the Polygon hackathon project.
You can find me here:
