Different branches get different instruments (well, the branch gets a assigned a 'lane' based on modulo of the initial branch commit, and the lane has an instrument).
I like the concept of 'structure of the history'. That's kinda what I hope the music captures. But... it's not quite there.
I like those suggestions - I had pentatonic at first but ended up liking the minimalism/Steve Reich of what is there now (including the 2nds when they hit). Adding a scale selector in the settings should be easy, and actually the timbre shouldn’t be too hard. Percussion I’ve thought about but need to experiment; I can’t get it to sound correct and have it responsive to the game.
Yeah, we could absolutely do a better job with solid interfaces for each service. To be clear, our nextjs apps, temporal workers, etc are all well defined, and changes in a single package are easily tested (and well tested). It's integration testing we struggle with.
And, there's always a tradeoff here between engineering & our real job as a startup, finding PMF and growth. That said, we want as much eng velocity as possible and a fast, solid integration testing platform/system/etc helps a ton with that.
So, it does sometimes duplicate code, especially where we have a packages/ directory of Typescript code, shared between two nextjs and some temporal workers. We 'solve' this with some AGENT.md rules, but it doesn't always work. It's still an open issue.
The quality is general good for what we're doing, but we review the heck out of it.
will email! Your homepage doesn't make the environment part clear - it reads like it's akin to cursor multiple agent mode (Which I think you had first, FWIW).
Man I was vim for life until cursor and the LLMs. For personal stuff I still do claude + vim because I love vim. I literally met my wife because I had a vim shirt on and she was an emacs user.
We do integration testing in a preview/staging env (and locally), and can do it via docker compose with some GitHub workflow magic (and used to do it that way, but setup really slowed us down).
What I want is a remote dev env that comes up when I create a new agent and is just like local. I can make the service but right now priorities aren’t that (as much as I would enjoy building that service, I personally love making dev tooling).
bit.io’s mission is to make data scientists and software engineers immediately productive, to remove obstacles to using data, and to make data more accessible. Join us in building a shareable cloud database where users can share their data with anyone in seconds just like a Google doc, query their data without worrying about compute or memory, and combine their data with a growing collection of immediately use-able open data. bit.io is transforming data in the same way GitHub transformed software and open source.
We're a seed-stage, well funded startup, 8 people right now and have just entered beta. We've solving hard problems in the database space and in the UX space, and we've got some really interesting engineering, data science, and special projects positions open.
I like the concept of 'structure of the history'. That's kinda what I hope the music captures. But... it's not quite there.