378 karma · joined July 26, 2011
Creator of https://plotly.express/ and https://react-pivottable.js.org/ and https://pivottable.js.org/
Personal Website: http://nicolas.kruchten.com/
Email first at last dot com.
Hex is changing the way people work with data. Our platform makes analytics workflows more powerful, collaborative, and shareable. Hex solves key pain points with today's data and analytics tooling, and is loved by thousands of users all over the world for the beautiful UI, new superpowers, and boundless flexibility.
We are a tight-knit crew of engineers, designers, and data aficionados. Our roadmap is full of big ideas and little details, and we would love your help bringing them to life.
Hex has raised over $100m from great VCs and angels, giving us many years of runway and the ability to pay competitive salaries, offer great benefits, and provide meaningful equity.
We're looking to grow our team with a second full-time Visualization Engineer (in addition to me!) working on no-code tools for visualization. See https://hex.tech/careers/visualization-engineer/ for more details.
Hex is changing the way people work with data. Our platform makes analytics workflows more powerful, collaborative, and shareable. Hex solves key pain points with today's data and analytics tooling, and is loved by thousands of users all over the world for the beautiful UI, new superpowers, and boundless flexibility.
We are a tight-knit crew of engineers, designers, and data aficionados. Our roadmap is full of big ideas and little details, and we would love your help bringing them to life.
Hex has raised over $100m from great VCs and angels, giving us many years of runway and the ability to pay competitive salaries, offer great benefits, and provide meaningful equity.
We're looking to grow our team with a second full-time Visualization Engineer (in addition to me!) working on no-code tools for visualization. See https://hex.tech/careers/visualization-engineer/ for more details.
Our metrics would maybe capture some aspects of consistency/viscosity, because `title` and `name` would both count towards vocabulary size, and because the distance between specs would be higher if `title` routinely needs to be changed to `name` when iterating, but that's about it. I don't believe a metrics-based approach like ours can quantify much if any of 'closeness of mapping' because that mostly happens in people's heads, not in the source code itself :)
Do the positions of the teams in the squares mean anything? It might be nice to have the teams laid out with two on top (rotated 45 degrees) with the top two being the current point leaders?
There's a neat overview of the landscape here https://www.youtube.com/watch?v=4a-Db1zhTEw