---
# System prepended metadata

title: Individual Ring Meeting Notes

---

# Individual Ring Meeting Notes
|  |  |
| -------- | -------- |
| Session title          | Development Tools/Ecosystem |
| Facilitator / Leader of the meeting            | Bogdan Habic |
| Helper (taking notes)                 | Still open for help |
| Time and date          | 15:00 20th August @ [Parity offices](http://bit.ly/2YYs60X) |
| Material requirements  | Whiteboard / WiFi / Screen |
| Number of participants | ~14 |

Attendees:  
# Summary 
As the Web3 ecosystem is growing so does the need for better and more ergonomic developer tooling.

# Background or expected changes
As the Web3 ecosystem is growing so does the need for better and more ergonomic developer tooling. In this session we will discuss:
- Missing ecosystem tooling
- Tool interoperability
- Traditional dev tools that can be ported over for Web3 purposes
- On-boarding new developers to the ecosystem
- Protocol compatibility and ergonomics

This doesn't mean you can't suggest/start a different conversation, as long as it has some significant connection to the ring meeting itself.

For this ring meeting, we have 3 hours reserved at the Parity offices and here is the suggested agenda:
- 15:00-15:15: People are gathering + room setup
- 15:15-15:45: Everyone introduces themselves, what they do, what are the problems they are solving
- 15:45-16:15: Brainstorming/Open discussion session regarding proposed topics
- 16:15-16:30: Break
- 16:30-17:45: Brainstorming/Open discussion session regarding proposed topics
- 17:45-18:00: Group feedback and final words

Please, if you have any suggestions or ideas, I'm more than happy to incorporate them in the agenda.

I'm here for any question:
- Telegram: @BogdanHabic
- E-Mail: bogdan@tenderly.dev

# Goals
- List of mission critical tooling that is missing right now in the ecosystem
- Possible compatibility / standardisation proposals
- List of missing tutorials / education materials

# Notes

- No single curated point how to start Eth/Web3 development
    - "Which version of web3 should I use?" "Maybe use a different lib?" "Where to get this information?"
- Onboarding different types of people should be different "Onboarding a C dev should be different than a Javascript dev"
- There should be an explanation of different dev tracks: protocol dev, dapp dev etc. x2
- If I didn't have someone to walk be through resources I would have a really hard time learning stuff
- Economics/incetives as part of development lifecycle
- No stability for low level libs -> the bar should be higher for quality
- Knowledge should be more compartmentalized
- Bugs that are happening now are much more subtle and you need to get them right the first time
- Better errors all around
    - Building good technical UIs
- Backward compatibility should be taken in consideration seriously
- Some queries / concepts are hard to simulate on ethereum (something that would be easy with SQL for example)
- Lack of a glossary
- Reverts are not specific enough even with revert strings
- ABI as a concept is to complex to grasp at the beginning
- Start looking at some of Solidity code as C shared libraries
- Hello World Dapps -> people don't know how to "pilot" the tech
- You need to know the whole stack even for the simplest of tasks
- A bunch of old code is used -> we need best practices
- More coordinated efforts should happen across the ecosystem