What if the Linear agent were to review every single code change and automatically merge those that are deemed relatively safe to land and don't introduce any regressions. Would that be of interest?
All of these are things that power users IMMEDIATELY notice and get annoyed. But there's no good way to report them, and the eng teams clearly are flying blind, patting themselves on the back how everything is up velocity-wise... but product quality got degraded! And they don't even know
In most of the world there is: no real willingness to solve problems nor an acceptance of people offering to solve their problems (out of pride) simply too much regulation so the problem cannot be solved without a license or long approval time very low standards of what is deemed acceptable so the problem isn't seen as a problem in the first place
Maybe Nix is like Rust: Amazing if you don't have to look at the code! I'm open to the idea that Omarchy Cinque could switch packaging system if I never have to look at nixlang, there are no ergonomic regressions, and we have full repo sovereignty.
As soon as you merge, it should be going out. You like you should have to stop the train to make your code not go into production as soon as you've merged.
it is always tempting to add this one feature that looks really cool but what you rarely think about is when you merge this feature it really means here's this pile of code that I don't that the person probably doesn't really understand that I don't fully understand
Anyone using GitHub knows that it isn't cut out for agents. The workflow, the review process, the merge queue and many things are made for the previous era.
And the solution is if people become part AI with some kind of neural link++ because what will happen as a result is that now the AI understands something and we understand it too like because now the understanding is transmitted wholesale.
We don’t think that the universe has had enough time to make them from stars that just merge. We know that two black holes can merge and make a bigger black hole and then those can merge and make a bigger black hole. We don’t think there’s been enough time for that.
However, with so many different software projects out there, each moving so rapidly and depending on and being used by so many other projects, it becomes practically-inevitable that some regressions "like that one" happen, almost constantly.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.