Earlier quoted context omitted.
> They'll re-invent/re-write things constantly Re-invent is fine, that's how we actually get the good stuff we use. Re-write (frequently) is usually a sign of bad power dynamics in the team, code rot and generally bad engineering management, in my experience. That's why most React shops end up in this vicious cycle of constant re-writes of a perfectly fine working system for this reason. Yeah, must be really nice get…
Sometimes I feel like the software field is just begging to be "disrupted" by AI. So much bad management and useless wheel-spinning, all with salaries far above what is typical for any given area. It's like taxis and Uber. Yes it's probably bad long-term that local taxi companies have been replaced by a mega-corporation. But there were so many bad taxi companies with rude dispatchers, lazy drivers, cars that show up…
Zed DeltaDB
321–329 of 329 posts
Re: Zed DeltaDB
#322Earlier quoted context omitted.
And the cherry on the cake: you get paid to work on your engineering project, get traction around it as opensource and if there is enough traction, leave the company and spin-off a new one to sell the same product to other companies! It's surely a lot of work but you get basically the discovery phase til market fit with your ass covered. Kudos to the engineers that pull that out, I really mean it!
That’s why nowadays every company will require that they legally own projects you work on during work hours unless explicitly asked. And many ask you to sign non compete clauses so you don’t take all the knowledge you acquired on the job to the competition, including your own projects, through this is quite hard to really enforce.
Re: Zed DeltaDB
#323Whoever on the zed team came up with this must be coding with agents way more than i am, because it hasn't come up for me as something I'd really need yet. But it sounds cool anyway. I guess it's kind of like undo history but persistent and with more visibility, and with branching? Anyone from zed here to comment?
The fallacy here is that if you have LLM then just start a new thread. That's what all vibe coders do anyways
Re: Zed DeltaDB
#324Earlier quoted context omitted.
That’s why nowadays every company will require that they legally own projects you work on during work hours unless explicitly asked. And many ask you to sign non compete clauses so you don’t take all the knowledge you acquired on the job to the competition, including your own projects, through this is quite hard to really enforce.
That seems to be common sense, is it not the default? That should be the norm if it isn't, it's like being a freelancer and being hired and publishing the project in your own name, that's borderline criminal imo.
Re: Zed DeltaDB
#325Earlier quoted context omitted.
The fallacy here is that if you have LLM then just start a new thread. That's what all vibe coders do anyways
Not sure I get what you're saying?
For any problem they just start chatting with LLM for 4 straight hours.
Re: Zed DeltaDB
#326Earlier quoted context omitted.
Right, my point being that it's should be up to the user to decide, because most of the times I run programs, I actually want them to be able to gobble up GB of disk, RAM and fully make use of my CPU. That's why I bought the hardware I have :)
Isn't that the default? The user has access to all available memory unless they (or an admin) set a restriction. Unavailable memory is only unavailable because writing to it crashes the kernel, thus preventing you from using your hardware!
Yes, it is, and for good reasons. That's why I disagreed with the original "An unprivileged userspace application, even if coded poorly, shouldn't crash the machine" part.
Re: Zed DeltaDB
#327Re: Zed DeltaDB
#328Re: Zed DeltaDB
#329Earlier quoted context omitted.
Isn't that the default? The user has access to all available memory unless they (or an admin) set a restriction. Unavailable memory is only unavailable because writing to it crashes the kernel, thus preventing you from using your hardware!
> Isn't that the default? Yes, it is, and for good reasons. That's why I disagreed with the original "An unprivileged userspace application, even if coded poorly, shouldn't crash the machine" part.