Thanks! We have a lot of respect for the work VikP and his team did on Surya but we haven't benchmarked his newer pipeline so I don't want to make a 1:1 claim.
If you want to do a side by side with your use case we'd be happy to set you up with free trial access.
I would love a Genius.com / annotation layer on top of these bills too. Just a dream I'm sharing out loud for no particular reason :) love govtrack in general otherwise!
It need not be shared , think more like a public notion/ share point document with comments visible . I.e experts(users) can create their own individual annotated versions and share with others .
As long as there is no single version of the annotations , moderation is not needed
I think the issue is that a person reading without an interlocutor has a better chance of getting some truth from the sum of the bill than reading with an “expert” bent on swaying them towards a fringe interpretation or even directly lying to distort the content. The feature lets them put on an air of factuality but really just inveigle people with a chopped take on a document.
Honestly it makes sense and resembles how other companies pay sales people. Lower base salary than other roles in the company for similar years of experience (roughly) but with a commission component that's some percentage of each sale. Commission is a big big part of sales culture that I suspect is hard to eliminate in an effort to be different.
What's interesting is that often times the commission has no cap, so top sales people can take home higher income than even than executives (at least in cash compensation).
But to the commenter's point, true transparency would share the commission % as well :)
The challenge of syncing from stubborn SaaS tools to your data warehouse / database I suspect is different than syncing data from your data warehouse / database back to SaaS tools. Specifically, reverse ETL has to incorporate more context from the business I guess so the data that lands in the 3rd party tools is actually solid.
Once you have customers and a good network of integrations with a large number of tools, I suspect it's easier to just buy that company than build it all yourself?
This is exactly right. We even went so far as to build a proof of concept internally, and the technical challenges are just very different. The simplest way to explain it is that Fivetran connects a skinny pipe (APIs) to a fat pipe (databases) while Census connects a fat pipe to a skinny pipe.
The data is only as solid as you make it to be. Ultimately reverse ETL is just a technology (basically from SQL to APIs). The quality/correctness of data is someone else's headache. I've been there and done that, and reverse ETL is a feature-product with huge churn. See how Hightouch pivoted hard from that into CDP.
>It’s more like a patchwork of locked treasure chests, each with its own key and its own label: this one funds scholarships, that one supports cancer research, another pays for upkeep on a library.
Explain why direct donations cannot accomplish the same. I suspect that universities want endowment donations because they grow tax free.
My understanding is that a large part of endowments comes from large (really, huge) donations.
If I was to donate 9 (or 10) figures to an institution, I would want to make sure it is used to support what I want it to support (cancer research, scholarships, libraries, etc), rather than be used as a general slush fund.
It's not entirely about what the organization wants, but also what the donators/sponsors want.
>If I was to donate 9 (or 10) figures to an institution, I would want to make sure it is used to support what I want it to support (cancer research, scholarships, libraries, etc), rather than be used as a general slush fund.
You can make that restricted donation outside of the endowment. I thought endowments were for the support of students, not research.
Compared to Bytewax, Slipstream puts the emphasis on freedom, at the cost of having to implement certain features yourself.
This freedom let's you do things that other libraries may not offer within the bounds of their API. For instance, I do see that joins and windows are supported in Bytewax, but is it possible to do more complex stateful joins based timestamps (temporal joins) or other arbitrary conditions?
If it does, then that's great. But I've had experiences where limitations became apparent during an end-phase of a project. When the API starts to reach its limits, but you're already invested in it quite deeply.
https://www.datalab.to/