mj2718

4 ms·

1.
Manage Ralph loops in a DAG pipeline with a Docker-like CLI(github.com)
1 points by mj2718 8mo ago|1 comments
2.
by mj2718 8mo ago
I made this tool so that you can have a pipeline that looks like the following: planner -> implementer -> reviewer Running for a number of iterations/loops, where it keeps building like a perpetual motion machine. I used it for 4
3.
I vibed a CMS with live-preview/users/click-through-edit in an afternoon(github.com)
2 points by mj2718 9mo ago|1 comments
4.
by mj2718 9mo ago
I hit a limit in a CMS that then wanted to charge $300 a month. So I got on the beers and vibed my own CMS with cursor in one afternoon. Agents are now coding better than most of us, but you still need to know wtf you're doing. The pro
5.
by mj2718 1y ago
Yep… this is what I expect as a baseline. This is also why I rarely use redis - Postgres at 100k TPS is perfectly fine for all my use cases, including high usage apps.
6.
by mj2718 1y ago
Sorry but if he’s using a setup that’s 20x worse than a regular laptop then I’m not really interested in his setup. To be fair, I asked the question and you found the answer - lol, my bad. Yes I agree using a nas that adds latency would red
7.
by mj2718 1y ago
My laptop running OOTB Postgres in docker does 100k requests per second with ~5ms latency. How are you getting 20x slower?
8.
by mj2718 2y ago
Of course it always depends, but my experience is people reach for distributed systems when they can simply run a single node. If you can run a single node, and it meets all your business requirements, then I’d argue that is simpler than ha
9.
by mj2718 4y ago
I wrote a blog post on this. We were using event sourcing and went with locking+batching method described. For other tables we wanted to read and move to a data warehouse we used the txid check. A bit hacky, but on AWS RDS we didn’t want to
10.
by mj2718 4y ago
Always found the first method of keeping bookmarks to the positions in a table to be the best method. I don’t think the 3 problems given to be an issue personally. - just loop at the interval that your users can accept the delay - querying