Paul-E

8 ms·

1.
by Paul-E 2mo ago
Legion Intelligence | Senior/Staff Backend Engineer | REMOTE (US) Legion is building a platform for governed agentic AI, primarily for government customers. Legion has interesting engineering challenges ahead of us, and we are looking
2.
Soft-deprecating chrono and chrono-tz(github.com)
3 points by Paul-E 2mo ago|0 comments
3.
by Paul-E 5mo ago
Obsidian seems like a perfect candidate for a WASM/WASI based plugin system that would properly sandbox plugin code.
4.
by Paul-E 7mo ago
When queries get complicated enough, you end up writing a custom query builder to build your SQL. Ceci n'est pas une pipe
5.
by Paul-E 7mo ago
> And, IMO, making dynamic queries harder is preferable. Dynamic queries are inherently unsafe. Sometimes necessary, however you have to start considering things like sql injection attacks with dynamic queries. Depends on what you mean b
6.
by Paul-E 7mo ago
I want to address this one point: > Similar thing can be said about writing SQL. I was really happy with using sqlx, which is a crate for compile-time checked SQL queries. By relying on macros in Rust, sqlx would execute the query agains
7.
by Paul-E 9mo ago
I haven't tested that, so I'm not sure if it would work. The import only inserts rows, it doesn't delete, so I don't think that is the cause of fragmentation. I suspect this line in the vacuum docs: > The VACUUM comma
8.
by Paul-E 9mo ago
That's pretty neat! I did something similar. I build a tool[1] to import the Project Arctic Shift dumps[2] of reddit into sqlite. It was mostly an exercise to experiment with Rust and SQLite (HN's two favorite topics). If you don&
9.
by Paul-E 9mo ago
I'm curious if you have tried SeaORM? I've used it a little bit (not too extensively) and really like it. It's like sqlalchemy in that you can declare your tables and have a type checked query builder, which is a big win IMO.
10.
by Paul-E 2y ago
This is what a number of startups, such as Yurts.ai and Vannevar Labs, are racing to build for organizations. I wouldn't be surprised if, in 5-10 years, most large corps and government agencies had these sort of LLM/RAGs over thei
11.
by Paul-E 3y ago
Has anyone tried to decentralize curation? Here is straw man proposal, similar to cert chains and webs of trust: Say I'm a "curator". I say on HN/Reddit/Discord "here is my key hash 'p2pcuration:185da2bc59
12.
by Paul-E 4y ago
A great paper on this topic is 'I've Got Nothing to Hide' and Other Misunderstandings of Privacy https://papers.ssrn.com/sol3/papers.cfm?abstract_id=998565
13.
by Paul-E 5y ago
Thank you for making this point. I didn't articulate it, but this is part of why I felt I had to say something.
14.
by Paul-E 5y ago
I've met Ross during my time at Princeton and he is a really genuine person, he is not trying to ruin anyone's life. This incident is the result of an uncharacteristic blind spot in empathy: a mistake. I also have experience with
15.
by Paul-E 6y ago
This paper was published when there were big fights going on about whether the block size should be increased. Om camp argued for the status quo, which was causing high transaction fees and long backlogs. The other camp argued for a larger
16.
by Paul-E 6y ago
One of the assumptions the authors make in this paper is that miners can turn their hardware on and off quickly, and that they will benefit financially for doing so. Mainly by paying lower electricity bills. It turns out the really big mine
17.
by Paul-E 6y ago
The paper that relies on turns out to have some inaccurate assumptions. The paper assumes that miners can flip their hardware on/off at essentially instantaneous intervals. The assume this to argue that miners will strategically turn t
18.
by Paul-E 7y ago
Location: Los Angeles / Irvine, CA Remote: Yes Willing to relocate: Yes, western USA Technologies: Python, Rust, Numpy, Cython, Jupyter notebook, Linux, git, bash LinkedIn: https://www.linkedin.com/in/ellenbogen&#x