n8agrin

I think an organization's governance structure being successful has more to do with how the people in the organization want to be governed than whether it's building an app or feeding the poor.

With full respect to your right to criticize, I don't understand what differentiates an organization trying to build a social networking app around biodiversity data from an organization feeding the poor, and those organizations' ability to experiment with their governance system. Can you expand that thought or is it rhetorical?

I've had similar thoughts. Any interest in sharing notes? Generally I've been thinking there should be a standard declarative format for data vis. This should be inspired by prior art like ggplot, Grammar of Graphics, Vega, VegaLite, etc.

From there it could be compiled to targets declarative or procedural (eg to generate VegaLite specs, echart specs or Observable Plot configs in JS).

How have you been thinking about this problem space?

:) Ty for being part of the community

:heart:

:heart:

iNaturalist was the final product of my Master's degree thesis team. I haven't contributed to it since school, about 11 years, so I don't deserve any credit for its success. The folks who have kept it alive are personal heros - they sacrificed a lot and invested so much to build the community that exists today. It's probably the project I'm still the proudest to have contributed to.

When we started, our goal was to encourage people to go outside and engage with the world around them. We dreamt that the data gathered by the community would be used in scientific research, but weren't confident it would ever reach enough of a critical mass. It has! More surprisingly, we had no idea how important iNat's image dataset would become for computer vision research.

Again, so proud of the folks who have helped to make iNaturalist thrive and so glad it still exists in the world.

In the context of a large client application, I often advise engineers that if we're optimizing things like the types of `for` loops we use, we've won the performance lottery. That is, I've never found a critical performance issue that is the result of using `forEach` instead of `for`.