- Wants me to blog every couple of weeks
- Can ask one of the engineers who is working on a cool project to blog about it during our meeting
- This is the lead developer relations role
- Doesn’t expect “big strides” in developer relations right now
- Should be able to address most Discord issues in a month
- “Bug” with up to one question per person per day
- Ask users to open issues on any bugs I see in Discord
- Build something with EdgeDB
- Follow getting started tutorial
- Make suggestions to improve
- Victor has lots of institutional knowledge about why decisions were made
- work closely with Victor and Yury
- Can clone individual repos in .repos and then symlink back to the .repos directory
Expectations
- Not trying to pull in loads of developers right now. Just need some limited visibility for now.
- Cloud is main product
- Cloud will remove the remaining DX hurdles
- Blog post in November
- Record tutorial
- Focus on learning the product
- Read the book
- Goal for the next couple of weeks:
- Follow book
- Build application
- Get involved in Discord
- Yury liked my persistence
- Likes Colin’s style in blog posts
- Talk to community about why they like EdgeDB and what can be built with it.
- Agree this is important, but it’s also on us to tell people why they need it.
- Read all of the blog posts
Origin
- Founded MagicStack in Canada
- hated consulting
- Philosophy on building products and data layer was unique and could be a product
- Originally a Python framework called Chaos
- Built on Postgres
- implementation detail
- No company is re-inventing everything at the same time
- EdgeDB is focused on replacing the front-end
- Reduce layers of abstraction
- As we grow, start messing with the engine
- Take postgres apart and re-assmble for their own needs
Advantages
- Speaks directly to programming language
- ORMs give you shallow capabilities
- SQL invented in 1976
- Modern query language is to SQL as Javascript is to COBOL
- Querying is not trivial with SQL, and is with EQL
- Mongo became popular because it was schemaless to avoid migrations, but schema is important
- Prisma
- High-level language to define schema
- Automatic migrations
- Protocols and APIs designed to work across a network and be resilient
- Vertically integrated: protocol, data model,