shayonj

7 ms·

61.
Mutable atomic deletes with Parquet backed columnar tables on S3(shayon.dev)
1 points by shayonj 1y ago|0 comments
62.
Mutable atomic deletes with Parquet backed columnar tables on S3(shayon.dev)
2 points by shayonj 1y ago|0 comments
63.
by shayonj 1y ago
I think ideally you could map retention of cold data to file objects itself and using key space naming strategy and lifecycle rules, expire the data that is not needed, thus saving on the storage costs (as much as possible hopefully)
64.
by shayonj 1y ago
Yeah , I poorly phrased it - I meant in an ideal situation with the benefits of parquet like columnar file structure. I very much understand that it’s not possible on parquet today for the reasons you mentioned and others.
65.
by shayonj 1y ago
Yeah. Or just sub out the data with null bytes. Something like that could be nice too.
66.
by shayonj 1y ago
Yeah, it mentions in few areas - compared to OLTP or similar workloads, this will definitely be slow
67.
by shayonj 1y ago
Thanks! looks like i messed up some css on my last frontend refresh a bit.
68.
An MVCC-like columnar table on S3 with constant-time deletes(shayon.dev)
45 points by shayonj 1y ago|9 comments
69.
Exploring PostgreSQL to Parquet archival for JSON data with S3 range reads(shayon.dev)
2 points by shayonj 1y ago|0 comments
70.
An MVCC-like columnar table on S3 with constant-time deletes(shayon.dev)
20 points by shayonj 1y ago|10 comments
71.
by shayonj 1y ago
That's fair. I had an EXPLAIN ANALYZE which shows the time it takes for planning and execution. And sending the query directly to the table outperforms that. More to come soon.
72.
Bypass PostgreSQL catalog overhead with direct partition hash calculations(shayon.dev)
35 points by shayonj 1y ago|13 comments
73.
Bypass PostgreSQL catalog overhead with direct partition hash calculations(shayon.dev)
2 points by shayonj 1y ago|0 comments
74.
by shayonj 1y ago
This is v cool! thanks for sharing
75.
The Tines AI Agent Action(tines.com)
1 points by shayonj 1y ago|0 comments
76.
by shayonj 1y ago
That’s a good distinction and thank you! AGI is indeed orthogonal to LLMs today.
77.
by shayonj 1y ago
Fair! I was going for more generic example for the intro and eventually segue into the greater point and questions the post is trying to make. It does touch on few other examples like the AlphaFold, later on.
78.
Is AGI Paradoxical?(shayon.dev)
4 points by shayonj 1y ago|5 comments
79.
by shayonj 1y ago
Very interesting concept. I’d love some cheap and “throw away” method of setting up tunnels with minimal onus on the exit nodes.
80.
We moved our ECS services from Fargate to EC2(tines.com)
2 points by shayonj 1y ago|0 comments
81.
by shayonj 1y ago
ok ok - i put in a little touch up :D
82.
by shayonj 1y ago
haha! I didn't see it that way originally. Shall take it as a compliment and rework that ToC UI a bit :D.
83.
by shayonj 1y ago
My experience hasn't changed between models, given the core issue mentioned in the article. Primarily I have used Gemini and Claude 3.x and 4. Some GPT 4.1 here and there. All via Cursor, some internal tools and Tines Workbench
84.
Pitfalls of premature closure with LLM assisted coding(shayon.dev)
5 points by shayonj 1y ago|0 comments
85.
Pitfalls of premature closure with LLM assisted coding(shayon.dev)
83 points by shayonj 1y ago|46 comments
86.
Pitfalls of premature closure with LLM assisted coding(shayon.dev)
1 points by shayonj 1y ago|0 comments
87.
Premature closure and the role of Senior Engineer in the world of AI(shayon.dev)
1 points by shayonj 1y ago|0 comments
88.
We moved our ECS services from Fargate to EC2(tines.com)
3 points by shayonj 1y ago|0 comments
89.
Short alphanumeric pseudo random identifiers in Postgres(andyatkinson.com)
2 points by shayonj 1y ago|0 comments
90.
Shipping Fast Requires a High Degree of Trust(shayon.dev)
1 points by shayonj 1y ago|0 comments

More ›