keks0r

5 ms·

1.
by keks0r 1mo ago
One of the things that was most challenging and still rough around the edges are backfills. Doing a BC breaking schema change in a chain of materialized view and repopulating can take a week or more for a big dataset. So having stable tooli
2.
by keks0r 3mo ago
Does this mean, that the full node compatibility purely depends on oxc for transpiling? So oxc compatibility = nub compatibility?
3.
by keks0r 3mo ago
How does this integrate with Git? is the CRDT stack mainly for syncronizing locally? and then "snapshotted" into git? Or how would the team collaboration part of this work?
4.
Show HN: Rudel – Claude Code / Codex sessions reveals 9 types of AI coder(app.rudel.ai)
5 points by keks0r 5mo ago|0 comments
5.
by keks0r 6mo ago
yes we had to tune the claude.md and the skill trigger quite a bit, to get it much better. But to be honest also 4.6 did improve it quite a bit. Did you run into your issues under 4.5 or 4.6?
6.
by keks0r 6mo ago
Team of 4 engineers, 1 data & business person, 1 design engineer. I would say roughly equal amount of sessions between them (very roughly) Also maybe 40% of coding sessions in large brownfield project. 50% greenfield, and remaining 10%
7.
by keks0r 6mo ago
We dont expect anything, we put it out there, and we might be able to build trust as well, but maybe you dont trust us, thats fair. You can still run it yourself. We are happy about everyone trying it out, either hosted or not. We are hosti
8.
by keks0r 6mo ago
1. can only partly be answered, because we can only capture the "edits" that are prompted, vs manual ones. 2. for us actually all of them, since we do everything with ai, and invest heavily and continously, to just reduce the amou
9.
by keks0r 6mo ago
the skill usage was one of these "I am wondering about...." things, and we just prompted it into the dashboard to undertand it. We have some of these "hunches" where its easier to analyze having sessions from everyone to
10.
by keks0r 6mo ago
We used it across the team, and when you want to bring metrics together across multiple people, its easier on a server, than local.
11.
by keks0r 6mo ago
Cool, whats the link? We have some learnings, especially in the "Skill guiding" part of our example.
12.
by keks0r 6mo ago
Our focus is a little bit more cross team, and in our internal version, we have also some continuous improvement monitoring, which we will probably release as well.
13.
by keks0r 6mo ago
The tool does have a quite detailed view for individual sessions. Which allows you to understand input and output much better, but obviously its still mysterious how the output is generated from that input.
14.
by keks0r 6mo ago
The 4% usage was about our internal team, and we have skills setup. So it is not necessary that they are not built, but rather that they were not used, when we expected them to be used. So we adapted our CLAUDE.md to make claude more eager
15.
by keks0r 6mo ago
Ohh this is exciting, I kinda overlooked it. I assume there are still a lot of differences, especially for accross teams. But I immediately ran it, when I saw your comment. Actually still running.
16.
by keks0r 6mo ago
It will be only enabled for the repo where you called the `enable` command. Or use the cli `upload` command for specific sessions. Or you can run your own instance, but we will need to add docs, on how to control the endpoint properly in th
17.
by keks0r 6mo ago
This is great. How are you "identifying" these stages in the session? Or is it just different slash commands / skills per stage? If its something generic enough, maybe we can build the analysis into it, so it works for your
18.
by keks0r 6mo ago
Ah sorry, the readme is more about how to run the repo. The "product" information is rather on the website: https://rudel.ai
19.
by keks0r 6mo ago
Its our own sessions, from our team, over the last 3 months. We used them to develop the product and learn about our usage. You are right, they will remain closed. But I am happy to share aggregated information, if you have specific questio
20.
by keks0r 6mo ago
The docker-compose contain everything you should need: https://github.com/obsessiondb/rudel/blob/main/docker-compos...
21.
by keks0r 6mo ago
There is also a docker setup in there to run everything locally.
22.
by keks0r 6mo ago
Yes we added codex support, but its not yet extensively tested. Session upload works, but we kinda have to still QA all the analytics extraction.
23.
Show HN: Rudel – Claude Code Session Analytics(github.com)
144 points by keks0r 6mo ago|86 comments
24.
Show HN: ObsessionDB – We rebuilt ClickHouse infrastructure to cut our costs 50%(obsessiondb.com)
12 points by keks0r 8mo ago|0 comments
25.
by keks0r 6y ago
Hey Hana & Josue, congrats on the launch. I like your approach of how to integrate it into products (via native React libs). I think you could go even a little bit further. One concern I would have is that by using your react library, I
26.
by keks0r 6y ago
Were also using Courier at laserfocus ( https://laserfocus.io ) for e-mail and it has been fantastic so far.