Basically it uses actix for the backend and yew (Vue-like rust frontend framework) for the frontend. This enables one to share types (and helper functions) between both, which is great:
Hey, I'm the lead engineer at Picterra. Would be happy to answer any questions.
What we are trying to do is indeed allow customers to build algorithms tailored to their use cases. We often joke that the reason our ML works is because we are overfitting to customer datasets/use cases. But I think that's somewhat true in the sense that we are not going for "worldwide trees counting" but more for "reliably count cars on these 50 parcels".
It's also interesting to note that a sizeable chunk of our revenue is coming from companies with drone data where it makes even more sense to be specific to customer data (resolution, time of day, geo, etc...).
Picterra | ML / Fullstack / Backend Engineers | Full-Time | REMOTE (EU only) or ONSITE (Lausanne, CH)
We are building a geospatial machine learning platform that allows users to detect any kind of object and train their own Deep Learning model in the cloud using an intuitive UI. That means we get to tackle interesting problems on a daily basis; from processing and visualizing large amounts of geospatial data to dynamically managing GPU workers, while exposing this to our users in a collaborative and intuitive web interface.
Our tech stack is Python/Django/Postgres on the backend and Vue on the front-end. We’re using PyTorch for our Deep Learning algorithms and deploy on Google Kubernetes Engine. We are working with geospatial data, so we are heavy users of GDAL, Mapbox, Leaflet, QGIS, and other GIS tools.
I would guess they have a system such that after a user has passed N captchas successfully, they trust its a human and start displaying them (a portion of) unlabelled captchas that will always succeed and that's when novel labelling happens.
Or something along those lines. And then you can get creative displaying same captcha to multiple users, etc...
https://github.com/julienr/liveboard-rs
Basically it uses actix for the backend and yew (Vue-like rust frontend framework) for the frontend. This enables one to share types (and helper functions) between both, which is great:
https://github.com/julienr/liveboard-rs/blob/master/shared/s...
That being said, I think maturity-wise, Typescript is probably a better bet for this right now, so I'll definitely look at trpc for $dayjob.