Zed is our office
81–90 of 343 posts
Re: Zed is our office
#82Re: Zed is our office
#83Earlier quoted context omitted.
Yes, but does it need all the ceremony surrounding it? If, every time I saved the file, the changes were analyzed and committed to git, and a useful commit message included, and commits squashed automatically and pushed and tested and tagged (using magic, let's say); if the system existed in the background, seamlessly, how would our interactions with source control and with other developers look?
automated commit message will tell you the "what" not the "why". In any circle of "what makes a good commit message and why even do it" discussions, invariably the recommendation is to explain the "why" and leave out the self-evident "what". If your stance is that commit and commit messages can be automated away then we might as well not even have them. I don't share this view, but yeah in this world we don't need AI…
Re: Zed is our office
#84I lost all faith and interest in Zed after they introduced AI features.
Re: Zed is our office
#85Re: Zed is our office
#86I lost all faith and interest in Zed after they introduced AI features.
Re: Zed is our office
#87I could imagine that in ten years git will feel strangely slow and ceremonial. Why not just continuously work and continuously deploy live-edited software
I feel the opposite way, that git branching and merging will become a bigger part of the job as more code is written by agents in parallel and then accepted by other agents or humans.
Re: Zed is our office
#88Re: Zed is our office
#89I lost all faith and interest in Zed after they introduced AI features.
Re: Zed is our office
#90I do wonder if we need a term for shoe-horned dogfooding though. Like sure, you can do this. You could do this in Figma! Or in Notion! Or in LEETCODE if you wanted to.
At least with Zed though, its plain text. If you find another way to collab realtime on plain text, you're not bound to 1 vendor.