77 karma · joined October 11, 2016
item, date, price
abc, 01/01/2023, $30
cde, 02/01/2023, $40
... 100k rows ...
subtotal. $1000
def, 03/01,2023, $20
"Hey Claude, what's the total from this file? > grep for headers > "Ah, I see column 3 is the price value" > SUM(C2:C) -> $2020 > "Great! I found your total!"
If you can find me an example of tech that can solve this at scale on large, diverse Excel formats, then I'll concede, but I haven't found something actually trustworthy for important data sets
Disclosure: My company builds ingestion pipelines for large multi-tab Excel files, PDFs, and CSVs.
I imagine we're not alone in this type of abstraction layer, and some type-safety would be very welcome there. I tried to build our system on top of Kysely (https://kysely.dev/) but the Clickhouse extension was not far along enough to make sense for our use-case. As such, we basically had to build our own parser that compiles down to sql, but there are many type-error edge cases, especially when we're joining in against data from S3 that could be CSV, Parquet, etc.
Side note: One of the things I love most about Clickhouse is how easy it is to combine data from multiple sources other than just the source database at query time. I imagine this makes the problem of building an ORM much harder as well, since you could need to build type-checking / ORM against sql queries to external databases, rather than to the source table itself
Given a model with pre-trained transcoders, it finds the circuit / attribution graph; i.e., it computes the direct effect that each non-zero transcoder feature, transcoder error node, and input token has on each other non-zero transcoder feature and output logit. Given an attribution graph, it visualizes this graph and allows you to annotate these features. Enables interventions on a model's transcoder features using the insights gained from the attribution graph; i.e. you can set features to arbitrary values, and observe how model output changes.
The blog post: https://www.anthropic.com/research/open-source-circuit-traci...
Syncopate builds tools to help automate financial diligence and management of long-tail financial assets.
We've found product market fit with ETL/analysis tools for niche financial data, starting with music rights, and we're looking to build out our capabilities across more Excel + PDF-based workflows.
What we're looking for: A full-stack engineer with experience building data-heavy applications. Experience with analytics databases like Clickhouse and data pipelining is a plus. Required to be knowledgeable in Typescript.
Big bonus points for: 1) High agency (previously a founder or built side-projects to completion) 2) Some knowledge of finance 3) Skill in Rust
You can reach out to me here https://www.linkedin.com/in/michael-markell-377b4221a/ or via email (michael at syncopate dot ai)
More about Syncopate (geared towards our music rights segment): https://syncopate.notion.site/
In the naive chunking approach, we would grab random sections of line items from these tables because they happen to reference some similar text to the search query, but there’s no guarantee the data pulled into context is complete.
It looks like Deepseek had a subdomain called "openai-us1.deepseek.com". What is a legitimate use-case for hosting an openai proxy(?) on your subdomain like this?
Not implying anything's off here, but it's interesting to me that this OpenAI entity is one of the few subdomains they have on their site
It’s like in chess, I know that the Sicilian is a good opening, that I’m supposed to play a6 in the najdorf, but I absolutely do not “understand” the Najdorf, and I do think it’s fundamentally past the limit of most humans understanding.
Without thinking terribly deeply about it, it seems like this could be modified to "what correlated mechanisms we're controlling for", in which case, yes I think if we controlled for the highly correlated variable of "does this cow live on a meat farm" with the mean age, we would be able to make broad claims about cattle lifespan without needing to be privy to the internal mechanisms of the agriculture industry
Insurance likes low variance outcomes because they’re easier to model accurately
The story may be different on Solana but it’s not really my area of expertise. My guess is many ethereum devs haven’t moved to solana because of its lesser decentralization.
Anecdotally I know a lot of ethereum devs are excited about building on layer 2s like zksync / arbitrum but there’s a learning curve and relatively little liquidity there too
Once you get above that, there’s a variety of FOSS you can self host, like jitsi and mediasoup (what pop.com uses.) There’s also some relatively cheap paid APIs like twilio and opentok.