babarock
Joined 15 years ago
Joined 15 years ago
The fact that we can fix things faster now doesn't mean that we should throw away caution and prevention. The specific point of his tweet is that we're seeing a lot of people starting to skip proper release engineering.
Agents are quick to fix bugs, yes, but it doesn't mean that users will tolerate software that gets completely broken after each new feature is introduced and takes a certain number of days to heal each time.
Clearly there's an advantage for being an early adopter, but the advantage is often overblown, and the cost to get it is often underestimated.
I've been an open source maintainer of one of the biggest open source projects in the world[1], and it wouldn't fill any of these requirements. Anybody else hates it that now "open source" is conflated with Github (a private company, itself not open source) popularity?
Code and feature still need to experience time and stability in order to achieve maturity. We need to give our end users time to try stuff, to shape their opinions and habits. We need to let everyone on the dev team take the time to update their mental model of the project as patches are merged. Heck, I've seen too many Product Owners incapable of telling you clearly what went in and out of the code over the previous 2 releases, and those are usually a few weeks apart.
Making individual tasks faster should give us more time to think in terms of quality and stability. Instead, people want to add more features more often.
Historically the term "Open Source" was specifically developed to divorce the movement from the "social good" ideas that were promoted by Free Software.
That's where I stand. I don't do Open Source to make the world better. I do Open Source because I believe that makes my software better.
I'm not an activist. I'm an engineer. Nothing wrong with activism, all the power to the people doing it, but the licensing I chose for my code doesn't take it into account.
I've written a ton of open source code and I never cared what people do with it, both "good" or "bad". I only want my code to be "useful". Not just to the people I agree with, but to anyone who needs to use a computer.
Of course, I'd rather people use my code to feed the poor than build weapons, but it's just a preference. My conviction is that my code is _freed_ from me and my individual preferences and shared for everyone to use.
I don't think my code is "stolen", if someone uses it to make themselves rich.
I'm not sure what's your point. Are you telling people who use org-mode that they shouldn't?
> We believe Italy, like all countries, has a right to regulate the content on networks inside its borders. But they must do so following the Rule of Law and principles of Due Process.
I live in Italy, I'm a citizen. I don't feel any safer having the internet regulated by a bunch of bureaucrats than I do state actors and bots.
I personally don't have any insight into the situation and I definitely don't want to defend big businesses, I'm just explaining what you're replying to.
If you consider that reviewer bandwidth is very limited in most projects AND that the volume of low-effort-AI-assisted PR has grown incredibly over the past year, now we have a spam problem.
Some of my engineers refuse to review a patch if they detect that it's AI-assisted. They're wrong, but I understand their pain.
"without attribution"?
Did we read the same article?
GDQ: Games Done Quick, the name of the Youtube channel.
OoT: Ocarina of Time, a beloved Zelda game from the 90s.
ACE: Arbitrary Code Execution. A vulnerability that lets you run whatever you want. You can use it to skip huge parts of the game, therefore achieving the fast speedrun
That being said, I agree with you, it does take a lot of time. To me, the switch occurred when I stopped considering this time "wasted" and instead consider it fulfilling. I actively look for the time I'll spend cooking each day, I believe it's a good use of my time and I don't try to rush through it.
The opinions I express here represent my own and not those of my employer.