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).
Apple has done a good job on the implementation and documentation for their confidential computing (https://security.apple.com/documentation/private-cloud-compu...) but of course it’s Apple only. There’s a few folks working on a non-Apple version of this, eg https://confident.security/ and others (disclaimer that I helped work on a very early version of this.
Read the Apple docs - they are very well written and accessible for the average HN reader.
Yep, often things are measured in FTE or FTE-equivalent units. It’s not precise of course but is a reasonable shorthand for the amount of work required.
SuSE doesn’t get enough credit for the quality of the distribution. Transactional updates, serious work towards a reproducible distribution, nano as an excellent container runtime, stability under large workloads - it’s a nice piece of engineering.
At bit.io, _if_ you ran the database on the free tier for the full month, it cost us around $0.83. We scaled to zero, so the most common case was that free tier DBs cost us about 1/30th of that. That database was running on its own pod, isolated from every other database.
I worked on YouTube transcoding about 12 years ago. First, the scale is mostly reused - what’s doing transcoding now is doing a different compute job later. Transcoding was also done for most videos only on idle compute. Second, Google had 300k+ caches around the world, in many surprising places (buses, cruise ships) as well as many thousands of other larger but not full data center locations; get the content as close as possible to the user. (I imagine now all transcoding from the mezzanine format is done in real time on an edge GPU for all but the most popular platforms and content). Tl;dr: build out a huge amount of infrastructure to serve ads very quickly and you can piggyback video serving on that at little marginal cost.
This would be a welcome change for folks running PG in k8s or with any external automated configuration management. Once you want to deploy Postgres databases via API to semi-trusted users you want to have configuration control outside of the database itself. We disabled this at bit.io via patches - would have been nice if upstream had this.
I like the concept of 'structure of the history'. That's kinda what I hope the music captures. But... it's not quite there.