jackmccloy

getting data into the hands of the right people is key, but i love how this project focuses much on building that context around the data.

a lot of the friction around using data boils down to ppl not having confidence that they're using it the right way.

Amplitude (YC W12) | Design Systems Engineer | SF or Remote

Amplitude’s mission is to help companies build better products. We are the analytics platform of choice for many top product teams around the world including Square, Paypal, and Notion.

We have several open roles across the organization, including an opening for a design systems engineer. You'll help build and enhance the foundation of Amplitude's UX using React, Typescript, and D3, as well as work on our frontend build system / tooling.

- Design Systems Engineer: https://boards.greenhouse.io/amplitude/jobs/5009720002

- All Open Roles: https://boards.greenhouse.io/amplitude/

The big advantage of declarative frameworks (not just React - many are moving in this direction) is that reasoning about your application's state becomes much easier. This is because when you take a declarative approach, your application's state is kept separate from the DOM, and the DOM is a function of the application's state.

Thanks man! It's possible, you just have to build an API endpoint to store the results across users. There's a section in the README on that - it shouldn't be too hard :-)

yaru22, github.com/bxh-io, and I built this because we wanted it to be easier to split test components inside React apps.

We also wanted there to be an A/B testing framework that works declaratively, the same way React does.

We'll be watching this thread for comments, questions, and feedback.

We plan to keep building this out, especially if there's a decent amount of interest in this approach to A/B testing.

Thanks for the feedback, and thanks for sharing.