Live data from Hacker News

Zed is our office

zed.dev

11–20 of 343 posts

Re: Zed is our office

#11
post #8

Zed is lovely and I hope it becomes super successful but this kind of mass collaboration might be ok for meeting minutes... maybe. But thinking of it for coding it gives me shingles. Code by mass live committee. Yikes.

It's just pair programming when you're doing it on code so if you can bear pair programming you'll be fine. Personally, I hate it.

Pair programming usually has a single "driver" on the keyboard to keep things controllable. Here, everybody is driving: "dozens of cursors are concurrently editing the same file in real-time."

Re: Zed is our office

#12
I _really really_ want to try this feature, but only if I can selfhost the collaboration server. If there is any way to do this, it's not obvious. Given that as I understand it, lots of project details will pass through Zed's servers, I can't imagine any enterprises would knowingly allow this without some kind of SLA with Zed.

Re: Zed is our office

#14
post #8

Earlier quoted context omitted.

It's just pair programming when you're doing it on code so if you can bear pair programming you'll be fine. Personally, I hate it.

Pair programming usually has a single "driver" on the keyboard to keep things controllable. Here, everybody is driving: "dozens of cursors are concurrently editing the same file in real-time."

That's not how they, or anyone else, uses it on code though - that's on their notes. This is just a feature, it's up to you how you use it.

Re: Zed is our office

#15
post #8

Earlier quoted context omitted.

It's just pair programming when you're doing it on code so if you can bear pair programming you'll be fine. Personally, I hate it.

Pair programming usually has a single "driver" on the keyboard to keep things controllable. Here, everybody is driving: "dozens of cursors are concurrently editing the same file in real-time."

The metaphorical infinite monkeys on typewriters.

Re: Zed is our office

#16

commence feature creep

The collaboration tools built into Zed have basically existed since the product launched. It is one of the primary drivers behind the product - they wanted to build the best editor for remote code collaboration.

Re: Zed is our office

#18

Zed is lovely and I hope it becomes super successful but this kind of mass collaboration might be ok for meeting minutes... maybe. But thinking of it for coding it gives me shingles. Code by mass live committee. Yikes.

I think it's a fun and interesting idea for training junior engineers and possibly for other use cases. Suggesting alternatives to (perceived) bad practices the instant you see them could be helpful for many people, and also save a lot of future time for reviewers.

I could also see it as a potential productivity aid. Person 1 sees Person 2 is writing something and they don't want to be seen as idle, so they start working as well. This might sound oppressive but a lot of people who struggle with ADHD/procrastination/akrasia actually receive great benefit from that structure. Similar to that startup that forces you to code while screensharing with a stranger in order to push you to work, or people who code in cafes/libraries to be more productive.

As long as it's not an organization requiring it for senior engineers, I could see promise to it as an eventual common new paradigm.

Re: Zed is our office

#19
I love Zed. I, mostly, love the direction they are taking the editor in.

But. There are now two times I see Zed going in the wrong direction. The AI integration was one. This feels like the wrong direction again.

I never really liked the AI integration. It felt off to me. I do love coding with Claude and I think I know why. It presents the "information I need to know" in a way my puny brain can handle it. Colored diffs. Summaries of what happened. It isn't perfect, but it has been incredibly productive for me. I never got that from Zed's AI integration; perhaps this has been improved, but I was up and running with Claude in a way that I never was with Zed.

This write-up sounds like "slack in my editor." If it is that, I hate it. Slack has destroyed company culture and communication. People, who are inherently lazy (I'm an old Perl programmer, so I can say that), have stopped thinking carefully and writing carefully, and in that void just throw the first thing in their head into a slack channel and think that is "collaboration" and "communication." It's toxic.

For example, this comment rubs me the wrong way: "Staff members hop in, volunteer to show off a cool feature or bug fix they worked on, and get real-time feedback from the rest of the team." I don't think our human brains work well with "real time feedback" UNLESS we have the information presented in a way that gives us massive clues on what's right and what's wrong. Reading a wall of text is not the way. A colorized git diff, or a video, or an entirely new way of presenting information might make real time feedback possible, but I am highly skeptical a text editor is the way or place to do that. And, I'm an emacs user and love text UIs, don't get me wrong.

Do I want to have "generalized one off rooms for things that don't fit anywhere?" I definitely don't want that. I want you AS THE AUTHOR to be really intentional about what's important and fit that into the proper channels. I need to know that information, but I don't want to know about, nor have the unspoken expectation that I SHOULD have known, about the other stuff. And, I want "managers" (if that still exists) to be carefully thinking about those channels and how the company is organized and push that structure down to people in the organization.

As Zed is the office, having one off rooms instead of in person coffee time feels very dangerous. That's the world a lot of people live in, but I don't like that office.

If this comment is the guiding light, then I'm worried: "We're building toward a future where collaboration is continuous conversation, not discrete commits—where every discussion, edit, and insight remains linked to the code as it evolves, accessible to both teammates and AI agents." I'm human, I have kids, I have other interests. A continuous conversation is impossible for me. I want discrete ideas, and right now, discrete commits and PRs are better, IMHO, than what I hear here. It's hard, but setting the expectation that to be successful I need to be paying attention to a river of information flowing by seems like a bad idea to me. I don't buy that Zed solves the problem of hiding the pieces of information that I don't need to see.

Oh hey! I have an idea. Why not use AI to summarize those conversations into discrete pieces!

I do love Zed. It is the best GUI editor out there. I know they will get it right. I just am skeptical about this direction and feel it misses the forest for the trees.

Re: Zed is our office

#20
post #8

Earlier quoted context omitted.

It's just pair programming when you're doing it on code so if you can bear pair programming you'll be fine. Personally, I hate it.

Pair programming usually has a single "driver" on the keyboard to keep things controllable. Here, everybody is driving: "dozens of cursors are concurrently editing the same file in real-time."

a few years ago our company used Screenhero which allowed editing with multiple cursors while screensharing.

The experience was actually quite nice for two-three people but we always had the "ok let me type now" flow. Multiple changes happening at once sounds hyper distracting.

Post reply on HN