The work product is not the work.

I'll probably get more hate for saying this but fine: I use Zed 50% of the time (the other 50% dedicated to vim) for two reasons:

1. It is fast and snappy. Nothing comes even close besides vim (and I don't mind going full time to it if I have to)

2. The ability to completely shut off and block any slop machine features from interfering with my workflow or leak code back to sloppenai, sloppus or any other self-installed-worst-security-practice-backdoor garbage.

Having said that, I hope they don't remove that ability in the future and enforce the "slop is so good man, you should try it" philosophy.

> Before agents, it was easier to believe that the ceremony of trading comments on snapshots was an effective way to collaborate on software,

I’m highly skeptical of this claim. For any complicated feature, there’s always a design doc (or an RFC, or a wireframe) and that’s what people used for discussion. Discussion in a PR are mostly about whether to accept the code, reject the feature, or provide feedback about alternate implementations. It’s not for pair programming or directing design.

Collaborating together in a research lab (brainstorm session) is not the same as asking feedback for a journal article (PR). What is described in the article is pair programming with extra steps.

I really like Zed. It's customisable enough for me to make it look how I want, it's faster than every other editor I've tried (scrolling is silk, zero lag anywhere), it has enough features that I don't need an IDE (debugger, refactoring tools), and it generally gets out of my way.

I also like the AI tools, the inline assistant is good and the agent is also pretty nice and well integrated into the editor without it being the focus point. I'm not against using AI but I certainly don't use it as much as a lot of people do.

That being said, I really dislike this recent push towards becoming more like a cursor wannabe. They have a new (for now) opt-in default layout that almost hides the editor panel in favour of the agent threads and agent panels. And now this. I don't want to switch editors, but if they keep pushing a different workflow from what I use it might send me back to Jetbrains...

Next up: a kit to wire up a developer's brain activity direct to the AI companies, so not a single part of their thought process remains in control of the developer, in order to feed the models. You must brainsignalmaxx 8 hours a day or be fired.

Your boss will also demand that you narrate your thought process 8 hours a day. Speakmaxxing will be required to keep your job. There will be a "silence" wall of shame for the non-compliers.

With LLMs now being responsible for the physical typing of code and mundane plumbing tasks, this is a wise direction to go into

Our human ability is not defined by our _absolute_ output, but, by the quality of the _delta_ applied to an engineering artefact

Great engineers obsess over every keystroke

With LLMs, a much smaller number of keystrokes can create a much larger and more positively impactful delta

Every delta to the codebase can tell us some informational property about the behaviour of the system and storing that information WILL prove to be useful in the future

Lmao an ad

[dead]

[dead]

[dead]