pgr0ss

6 ms·

1.
Advent of Management(github.com)
5 points by pgr0ss 9mo ago|0 comments
2.
by pgr0ss 1y ago
My idea for for this to add metadata to the transfers, likely with a jsonb column. But I agree that the ledger won't encompass everything. You would still have other database tables and then you'd store domain identifiers in the l
3.
by pgr0ss 1y ago
I updated the README and added an example test: https://github.com/pgr0ss/pgledger?tab=readme-ov-file#histor...
4.
by pgr0ss 1y ago
The idea is that the ledger implementation itself is generic and shared, and then how you use the ledger is the novel part.
5.
by pgr0ss 1y ago
> how do we efficiently get the balance of a certain account at a certain date time? This depends on how you implement the ledger. For pgledger, I store the balance in every entry, so to find a historical balance, you just need to find t
6.
Double-Entry Ledgers: The Missing Primitive in Modern Software(pgrs.net)
56 points by pgr0ss 1y ago|18 comments
7.
Double-Entry Ledgers: The Missing Primitive in Modern Software(pgrs.net)
3 points by pgr0ss 1y ago|0 comments
8.
Visualizing Financial Data with DuckDB and Plotly(pgrs.net)
1 points by pgr0ss 1y ago|0 comments
9.
A Ledger in PostgreSQL Is Fast(pgrs.net)
4 points by pgr0ss 1y ago|0 comments
10.
The Next Generation of the Heroku Platform(blog.heroku.com)
3 points by pgr0ss 2y ago|0 comments
11.
DuckDB over Pandas/Polars(pgrs.net)
56 points by pgr0ss 2y ago|42 comments
12.
The Many Ways to Read Tech News(pgrs.net)
1 points by pgr0ss 2y ago|0 comments
13.
by pgr0ss 2y ago
I think that's a fair point. Unnesting arrays in SQL can be annoying. Here is your first example with duckdb: duckdb -c \ "select * from ( \ select unnest(assets)->>'browser_download_url' as url \
14.
DuckDB as the New jq(pgrs.net)
364 points by pgr0ss 2y ago|73 comments
15.
by pgr0ss 3y ago
Hi, I’m the author of the blog post. > And it is bizarre to me that you could run a payments system without high-availability or immutability at its core. I’m not sure what you’re referring to here as my post didn’t really go into these
16.
Lessons Learned from Payments Startups(pgrs.net)
2 points by pgr0ss 3y ago|0 comments
17.
ULID Identifiers and ULID Tools Website(pgrs.net)
1 points by pgr0ss 4y ago|0 comments
18.
Three Sisters (Agriculture)(en.wikipedia.org)
2 points by pgr0ss 4y ago|0 comments
19.
by pgr0ss 5y ago
It was also covered in: https://www.braintreepayments.com/blog/switching-datacenters...
20.
General Availability of Braintree GraphQL API(medium.com)
8 points by pgr0ss 7y ago|0 comments
21.
Deploying Phoenix to Kubernetes from Scratch(quan.io)
3 points by pgr0ss 7y ago|0 comments
22.
A Year on TC39: Dispatches from the Future of JavaScript(medium.com)
8 points by pgr0ss 8y ago|1 comments
23.
Continuous Deployment Isn’t Just for Applications(medium.com)
3 points by pgr0ss 8y ago|0 comments
24.
Dependency Injection in Go(blog.drewolson.org)
2 points by pgr0ss 8y ago|0 comments
25.
GraphQL at Braintree(braintreepayments.com)
5 points by pgr0ss 8y ago|0 comments
26.
Dropwizard Can Be Simple(pgrs.net)
2 points by pgr0ss 10y ago|0 comments
27.
Steal a Credit Card – Buy a Hoverboard(buzzfeed.com)
2 points by pgr0ss 11y ago|0 comments
28.
Java REPL with JShell and Bazel(pgrs.net)
1 points by pgr0ss 11y ago|0 comments
29.
Migrating from Gradle to Bazel(pgrs.net)
4 points by pgr0ss 11y ago|0 comments
30.
Elixir Streams(blog.drewolson.org)
152 points by pgr0ss 11y ago|16 comments

More ›