If I'm playing a quick pattern like this and holding down some bass note, depending on where the pattern starts, the middle two notes will become "synchronized" and play/get recorded at the same time. In my example, the top 4 notes work fine, but shifting down by one note causes the bug. I also switched between holding the bass not and not for demonstration. I assure you my fingers aren't doing anything different, I messed around with this for a while.
edit: got a better recording: https://webpiano.jcurcioconsulting.com/play/b4qautCGQpQjA6wq...
2nd edit: I thought this had to do with the "groupings" of keys but even the middle 4 that are grouped together show this behavior: https://webpiano.jcurcioconsulting.com/play/5XuIskeJNQQaiC7h...
The Claude the industry needs is one that responds to that prompt with questions about scope and intent, and challenges its only-suitable-for-tutorials design ideas rather than obediently delivering a "90% finished product".
10 years ago, this basically marks the difference between hiring some dude on Fiverr for $400 and an actual engineer or agency who might help you figure out what the heck you're trying to do and point you in some sane direction towards it.
I appreciate this article for sharing what kind of experience people can expect from Claude right now, but it mostly demonstrates that code assistants remain most useful in the hands of experts who are careful what to ask for, and largely misleading and slop-amplifying for people who don't.
"Ask questions for clarification as needed."
Claude will then present a list of questions I answer, either directly, or sometimes those prompt more thought or questions from myself.
Either way, that statement helps escape the assumption that I just want some slop reaching the goal in the quickest way possible.
I work with a very large ( 280+ project ) .NET semi-monolithic semi-services code base with internal nuget packages.
I've only a handful of times hit the limits on a team plan and even then only minutes before the window refreshes.
I'll chime in with some of my workflow and tips when I have a more appropriate place to do so as it feels disrespectfully off-topic to elaborate further here about too much .NET specific.
As a general tip for working with large code-bases, if you have:
/docs
/src
/src/projectA
/src/sub-projectB
/src/sub-projectC
/src/sub-sub-depdencyD
/tests/
Then don't just run claude at the root directory (/).
Run it in ./src/projectA and then use /add-dir to bring in only the depenedencies you care about for the problem you're working on.
Or even run it in /docs and then bring in just the places where it needs.
It will prompt to ask to read from / semi-often, but you can just deny it, either explicitly through claude.settings.local, or just through a prompt for that action.
By carefully controlling the scope, you limit what it tries to read. If you catch it trying to read from /sub-project-B and you think it's irrelevant, you can not just deny it, but ask it why it thought it wanted to read from it, and then update your documentation (or your priors) appropriately.
I've found the worst time for just blowing through credits / usage is when I hit a problem that's just not solvable, but more on that another time.
Anyways, I do appreciate the tips. I am going to attempt to not use Sonnet 4.5 for planning and see if opus does a better job of limiting scope.
eterm•1mo ago
( p.s. Tell claude that when quickly pressing keys with a mouse that there is audible clipping. This doesn't seem to happen when using the keyboard. )
Jeremy1026•1mo ago
If I come back to it to look to add polish (and fix mobile) that'll be a prompt I'll throw at it as well.