maximilianroos

self-promotion, but check out worktrunk.dev

by far the most popular worktree manager

Thanks!

I think at the moment that's indeed the case...

But also maybe that will change — LLMs can learn new languages faster than people, and can _write_ new languages much faster than people. So wide confidence bounds for the future!

Maintainer here!

Indeed we're doing fewer new features (and haven't posted to the posts page in a long time, as you noticed).

But it's still maintained, folks are still using it, if anyone finds bugs in simple-to-moderate queries then we'll fix them.

LLMs probably took a bit of the wind out of our sails for making this "the new standard". But I still think it's a really nice language and interface; if the world changed again such that it became more widely useful, I'd jump to spending lots of time on it again.

He explicitly disavowed any crypto / coin endorsement

(I don't _love_ his vibes on Twitter, but he seems like a very reasonable guy generally, and the project seems awesome)

What did you think "building social skills" meant? vibe coded apps?

Gotta start somewhere!

I'm all for building apps to solve problems, but I would really encourage folks to ask people politely to do what you want them to do, rather than having an app do it for you.

You can just ask people for things! And you will become a better person for it.

Very excited to see this!

I've been working on a worktree manager for a couple months, excited to share it.

Since agents have become good enough to run in parallel, I've found git worktrees to be, in the words of Juliet "my only love sprung from my only hate" — an awesome productivity multiplier, but with a terrible UX...

Worktrunk is designed to fix that: 1) it's a wonderful layer on top of git worktrees and 2) it adds a lot of optional QoL improvements focused on parallel agents.

Those Qol improvements include a command to show the status of all worktrees/branches (including CI status & links to PRs), a great Claude Code statusline, a command to have an LLM write a commit message, etc.

Like my other projects (PRQL, xarray, insta, numbagg), it's Open Source, no commercial intent. It's written in rust, extensively tested; crafted with love (no slop!)

Check it out, please let me know any feedback, either here or in GH. Thanks in advance, Max

- https://github.com/max-sixty/worktrunk

- https://worktrunk.dev/

Have your AI talk to their AI

Then, if the AIs are positive, the human principals can talk

Seems quite reasonable!

thanks!

> One of the challenges faced by our Java service was its inability to quickly provision and decommission instances due to the overhead of the JVM. ... To efficiently manage this, we aim to scale down when demand is low and scale up as demand peaks in different regions.

but this seems to be a totally asynchronous service with extremely liberal latency requirements:

> On a regular interval, Password Monitoring checks a user’s passwords against a continuously updated and curated list of passwords that are known to have been exposed in a leak.

why not just run the checks at the backend's discretion?

I posted some notes from a full setup I've built for myself with worktrees: https://github.com/anthropics/claude-code/issues/1052

I haven't productized it though; uzi looks great!

that's a great hierarchy!

though what does "static cpu" vs "dynamic cpu" mean? it's one thing to be pointer chasing and missing the cache like OCaml can, it's another to be running a full interpreter loop to add two numbers like python does

Big fan of QStudio! Thanks for building it!

SQL is terrible at allowing this sort of transformation.

One benefit of PRQL [disclaimer: maintainer] is that it's simple to add additional logic — just add a line filtering the result:

  from users
  derive [full_name = name || ' ' || surname]
  filter id == 42           # conditionally added only if needed
  filter username == param  # again, only if the param is present
  take 50

That's a facially absurd statement. Just on the numbers:

The US consumes 500 gigawatts on average, or 5000 watts per household.

So if every household bought an 8K TV, turned it on literally 100% of the time, and didn't reduce their use of their old TV, it would represent a 10% increase in power consumption.

The carbon emissions from residential power generation have approximately halved in the past 20 years. So even with the wildest assumptions, it doesn't "throw away all the progress we've made on Global Warming for the past 20 years ...".

Sounds like the coach helped you maintain eye-contact with the camera. But if we get a tool to do this, then we're lying. Would you say the coach helped you lie?

> He prefers his own “escalatory approach”, working through a system via an administrator’s access and searching for a “confluence”, a collection of information shared in one place, such as a workplace intranet.

Was this a mistaken transcription for Confluence, the Atlassian app?

Move on to what? ARM? Is ARM better in every way than x86?

(genuine question)

An alternative is to automatically merge dependency changes which pass the tests. Then there's no need for any intervention unless something needs your attention, just dismiss the notification.

We do this at PRQL, with: https://github.com/PRQL/prql/blob/12b1bb65afd5b67f34b98d0ac1...

Even GitHub-hosted Pages are down — https://prql-lang.org/ is also a unicorn

Source?

How are you going to finance a capital-intensive business from employees? Are you going to build a nuclear reactor with sweat equity?

Happy to see them making the correct prioritization

Having non-profits pay property taxes — similarly to how they pay employer taxes — seems like a good step. Property taxes are in part a fee for benefits which non-profits receive.

It would also incentivize local governments to encourage the growth of non-profits. Currently Cambridge's tax revenue is negatively affected by Harvard's growth...

I have the opposite reaction — I'm not surprised at all!

The short-term benefits seem really high. And ADHD sits at one end of a normal distribution — lots of people suffer from elements of it, particularly when doing solitary work which requires lots of concentration.

If landlords were restricting supply in order to increase rents, we'd see higher vacancy rates in locations with higher rents.

But we see the opposite — NYC has a vacancy rate of 1.4% and peak rental pricing.

It addresses the problem of housing costs for long-term residents, we agree.

It does that in two ways — it prevents tourists from competing for their house, and it reduces tourism, reducing local wages, which reduces housing demand from other locals.

But that's bad! It's bad for the tourists and it's overall bad for the locals. It would be even faster to just prevent all exports from Hawaii, including tourism — housing prices would drop really quickly. Would you advocate for that?

Instead, the goal should be to _increase_ the amount that people can trade, so you get some value from seeing a beach in Hawaii for a week and someone who lives in Hawaii can rent out their house or work in an airport or build a sightseeing business. And we can do that through allowing more stuff — including houses — to be built!

> You could approve more building, but then more people would move in until prices were high again. The area is so appealing that no matter how much housing there was, people would flood in until it became saturated again.

If supply has no effect on price, then banning AirBnBs won't reduce prices either

[PRQL dev here]

Love what you've done and thanks for building on PRQL!

We're very happy to add something like a PIVOT statement. In the long term, we'd have to think about how to make it work deeply in PRQL, since the column names are suddenly runtime dependent. In the short term, we should definitely make PRQL work for your case — it's important that there's an escape hatch for things that aren't natively supported by PRQL yet. (We have s-strings but I'm guessing they don't cover this specific case?)