# RAD/DAD
Rapid DAO application development at DAOhaus.
---
## What is RAD?
### Rapid Application Development
- Build as fast as possible
- Separate business logic from logic that is common across all apps
- Turn common logic into reusable tools
- Build tools to help build tools
- So that developers only need to worry about the business logic for each app
---
## Why?
- Apps are cattle, not pets
- DAOs are new. No one knows what the hell works.
- We need to test coordination mechanisms instead of writing the same JS over and over.
- Web3 dev is hard, but doesn't need to be. We have opportinities that have never existed before
- We all use the same API
- and the same database
- We should be using the same models
- Being able to use the permaweb allows to build in ways we haven't before
---
## What is DAD?
### DAO/Distributed Application Development
- Build tools that help tackle the common challenges of DAO dev as fast as possible
- Use the web3 APIs to distribute the logic over many apps to keep things simple (at least to start)
- Prototype the model fast, learn how the community coordinates
- Then, once your DAO or DAO is flush with cash, build something beautiful and custom
- Reduce forms, on chain TXs, fields, contract interfaces, and more to what we call DAO blocks or legos. We can do a lot more with static data + we don't need to maintain static data.
- Apps become interpreters.
- Frontends have a new way of talking to eachother (legos + permaweb), so in the future we can leverage that for even faster gains
---
### Why?
- Life is too short
- DAO dev is very challenging
- multicall
- polling
- has to interact with the rest of Web3
- shamans
- endless piles of forms
- endless integrations
- Not displaying data is a severe vulnerability
- Most in the community rely on the front end, not etherscan
- If we have to tackle the above problems over and over, we will never get to the custom business logic that each DAO has.
- Every DAO is different, will eventually require its own app. Every community will need its own mechanisms.
- So that developers only need to worry about the business logic for each app
---
## Today/Tomorrow
---
## Session 1
- Explain RAD/DAD
- Take a look at Dekan's shaman contract (https://blockscout.com/xdai/mainnet/address/0xbC9364441E42f3bbA5D5bB9A6c113E6D46026c14#code)
- Take a look at Free Ryder DAO on admin interface (https://admin.daohaus.fun/#/molochv3/0x64/0x7e72ba58d3d331d339566db9ff3ec184b293477d/members)
- Take a look at the app we'll be building (https://freeryder.daohaus.club/)
- Do a rough walk through of the code
- QA
---
## Session 2
- Build from the starter
- Update routes
- Build out structure, add contexts, show what's in there already
- Build useClaim hook
- Start Claims page
- QA
---
## Session 3
- Get ABI
- Build TX and contract lego
- Build Claims page
- Add finishing touches to Home page
- If time build leaderboard
- QA
<style>
.reveal {
font-size: 1.75em;
}
.reveal section {
text-align: left;
margin-left: auto;
margin-right: auto;
}
</style>
{"metaMigratedAt":"2023-06-17T16:23:25.855Z","metaMigratedFrom":"Content","title":"RAD/DAD","breaks":true,"contributors":"[{\"id\":\"1f0e5e36-6d79-4fae-8c10-a38ec6574193\",\"add\":3136,\"del\":4}]"}