4 ms·

Sniffly – Claude Code Analytics Dashboard

41 points by rand_num_gen 1y ago

deleted 1y ago
[deleted]
rand_num_gen 1y ago
I’ve always wanted to do an analysis of how I use Claude Code. Then I found out that someone had already done it. I looked at my own usage data, and for now, there’s nothing particularly interesting. I wonder if anyone has any ideas.
- dpflan 1y ago
  What’re you hoping or have some intuition you’ll discover/learn?
  - rand_num_gen 1y ago
    https://blog.continue.dev/intervention-rates-are-the-new-build-times/ https://blog.continue.dev/intervention-rates-are-the-new-bui... For example, error type distribution or intervention rates. This can tell me how efficient I am when using Claude. But currently, the error type is a bit too broad, and I haven’t discovered much yet.
philipp-gayret 1y ago
How does this compare with Claude Code's native OTEL reporting? Having a quick look at the codebase it looks like it parses your local Claude Code JSON files, why?
saejox 1y ago
I fear for the variety in the internet coding culture. Significant portion of code is being written by ai, all looks the same, all has the same mediocre quality. Even the github page descriptions are generated with ai, overflowing with emojis and same sentence structures repeated.
- diggan 1y ago
  > I fear for the variety in the internet coding culture. Significant portion of code is being written by ai, all looks the same, all has the same mediocre quality. Who cares who actually "typed" it? Shit code will be shit code regardless of author, there is just more of it now compared to before, just like there was more 10 years ago compared to 20 years, as the barriers for getting started is lowered time and time again. Hopefully, it'll be a net-positive, just like previous times, it's never been easier to write code to solve your own specific personal problems. Developers who have strict requirements on the code they "produce" will make the LLM fit with their requirements when needed, and "sloppy" developers will continue to publish spaghetti code, regardless of LLMs existence. I don't get the whole "vibe-coding" thing because clearly most of the code LLMs produce is really horrible, but with good prompting, strict reviews and not accepting bad changes just to move forward lets you mold the code into something acceptable. (I have not looked at this specific project's code, so not sure this applies to this project, but is more of a general view obviously)
  - jasonjmcghee 1y ago
    I think the issue is, you used to be able to tell at a glance how much effort someone put into a project (among other things) and that would give you a reasonable approximation of what to expect from the project itself. But now the signals are much harder to read. People post polished looking libraries / tools with boastful convincing claims about what they can do for you, yet they didn't even bother to check if they work at all, just wasting everyone's time. It's a weird new world.
    - tough 1y ago
      It's fake polish, but at the end of the day you have always to check whats in the codebase if you're gonna vendor it in or adopt it as a dep imho if anything the smelly readme's that look all like claude wrote them, are a good tell to check deeper
    - another_twist 1y ago
      I think you should never do that. Who cares how much effort went into something ? Its the result that matters.
PanMan 1y ago
Feature suggestion: Costs (and tokens) per branch. I'm interested what branches we spend the most on.
- anotheryou 1y ago
  another one: overall stats (same as per project)
tough 1y ago
I do use AI for vibe coding a lot of slop, but I make a favour to myself and the world and keep those repo's mostly private. Nobody should publish slop code AI assisted or not tbh

41 points by rand_num_gen 1y ago

deleted 1y ago

[deleted]

I’ve always wanted to do an analysis of how I use Claude Code. Then I found out that someone had already done it. I looked at my own usage data, and for now, there’s nothing particularly interesting. I wonder if anyone has any ideas.

dpflan 1y ago
What’re you hoping or have some intuition you’ll discover/learn?
- rand_num_gen 1y ago
  https://blog.continue.dev/intervention-rates-are-the-new-build-times/ https://blog.continue.dev/intervention-rates-are-the-new-bui... For example, error type distribution or intervention rates. This can tell me how efficient I am when using Claude. But currently, the error type is a bit too broad, and I haven’t discovered much yet.

philipp-gayret 1y ago

How does this compare with Claude Code's native OTEL reporting? Having a quick look at the codebase it looks like it parses your local Claude Code JSON files, why?

saejox 1y ago

I fear for the variety in the internet coding culture. Significant portion of code is being written by ai, all looks the same, all has the same mediocre quality. Even the github page descriptions are generated with ai, overflowing with emojis and same sentence structures repeated.

diggan 1y ago
> I fear for the variety in the internet coding culture. Significant portion of code is being written by ai, all looks the same, all has the same mediocre quality. Who cares who actually "typed" it? Shit code will be shit code regardless of author, there is just more of it now compared to before, just like there was more 10 years ago compared to 20 years, as the barriers for getting started is lowered time and time again. Hopefully, it'll be a net-positive, just like previous times, it's never been easier to write code to solve your own specific personal problems. Developers who have strict requirements on the code they "produce" will make the LLM fit with their requirements when needed, and "sloppy" developers will continue to publish spaghetti code, regardless of LLMs existence. I don't get the whole "vibe-coding" thing because clearly most of the code LLMs produce is really horrible, but with good prompting, strict reviews and not accepting bad changes just to move forward lets you mold the code into something acceptable. (I have not looked at this specific project's code, so not sure this applies to this project, but is more of a general view obviously)
- jasonjmcghee 1y ago
  I think the issue is, you used to be able to tell at a glance how much effort someone put into a project (among other things) and that would give you a reasonable approximation of what to expect from the project itself. But now the signals are much harder to read. People post polished looking libraries / tools with boastful convincing claims about what they can do for you, yet they didn't even bother to check if they work at all, just wasting everyone's time. It's a weird new world.
  - tough 1y ago
    It's fake polish, but at the end of the day you have always to check whats in the codebase if you're gonna vendor it in or adopt it as a dep imho if anything the smelly readme's that look all like claude wrote them, are a good tell to check deeper
  - another_twist 1y ago
    I think you should never do that. Who cares how much effort went into something ? Its the result that matters.

PanMan 1y ago

Feature suggestion: Costs (and tokens) per branch. I'm interested what branches we spend the most on.

anotheryou 1y ago
another one: overall stats (same as per project)

tough 1y ago

I do use AI for vibe coding a lot of slop, but I make a favour to myself and the world and keep those repo's mostly private. Nobody should publish slop code AI assisted or not tbh