Ironically I rather like the fact that OoenBSD’s culture is a bit anti-user.
In my older age I’m discovering that being regarded with derision is another type of respect. Linux, like Windows before it, caters to its users. The BSD’s respect you enough to assume you’re smart enough to cater to it.
It helps that kernel code base is orders of magnitude smaller than the Linux kernel.
Linux accepts LLM code so I swapped to OpenBSD. It’s a shame but I really love the community and humanity that comes from people, human beings, working together towards a goal.
I used Gentoo for a while before that and loved it but, alas, the community and Linux as a whole just doesn’t share my values.
I would say, for anyone using Linux and looking for a change of pace, OpenBSD is awesome and is still in that space of “respecting the user”
Fully this.
In my day to day life it improves nothing. I certainly could write a complicated harness over a local model to get it to automate a ton of my day to day tasks but… Why?
Why would I do that? Regular deterministic tools and regular programming languages already give me the ability to automate the stuff that is truly tedious. Aside from that most of the tasks that people seem to use it for are tasks were the friction of doing them is were all the benefit lies.
People using this shit for journaling or taking notes is INSANE.
Yeah yeah yeah
But the problem is it will be used to disarm leftists. This regime has already displayed a preference for selectively applying the law to political enemies.
It would be wise for those of us that share a common, human-first, political position to make ourselves extremely unpleasant to interact with. Ideally in large, mobile, groups.
All the money in the world cannot render someone immune to kinetic energy
Create semipermeable intentional communities that center around convivial technology and human empowerment?
For real, this isn’t going to get better and every day that passes I ask myself “what is this actually buying me? Do I even like this?”
I know the common refrain is we can’t “bury our heads in the sand” but history tells us that humans take the path of least resistance and that path is the “sloppening”
What a young account to come into this world, arrive in this thread about an AI violating containment, and then tell an unrelated anecdote about how well an AI agent did a vaguely complicated task when properly harnessed.
Certainly a human being is on the other side of this post and not, say, one of the countless bots out of Eglin AFB.
Certainly
I don’t know I kind of like it.
It’s fun and makes my brain do a few pushups
I can not tell you how tired of seeing these vibe coded projects I am.
You didn’t give nearly enough of a shit to write the application, why should I give enough of a shit to use it? Could you explain, in detail, line by line, what the happy path of a standard web request is in this thing? Could you walk me through the specific engineering decisions that were made and why? Could you point to the specific regions of code that reflect those engineering decisions?
I’m beyond exhausted with these things and honestly I’ve gotten to the point where I’d like for us to ban non-codeberg repos
My honest, biggest, fear is that AI coding does not, in the long run, drive up bugs and security issues. That is the only tangible piece of data we have to point to as a counter argument to this tool. If not for that businesses will not care about consistency, only that the agents can read and understand it.
If I was a betting man I would say that security engineering is going to see a spike in demand in the next few years as a by-product of this.
But that’s probably cope.
I’m with you comrade. It’s tough raising a kid in this world but as far as I see it we’re playing the long game now.
Gotta believe that our way of doing things wins out over time. Along with other, more direct, strategies.
You joke but that’s basically the conclusion of both the newer agent studies and the older Xerox park study on peripheral use. Language and logic are stored in an easier to access location in the brain than the kinds of skills used in architecture and planning.
To be clear, I’m no rube. I recognize that these are powerful tools. But I suppose my take here is that if an LLM is necessary to get rid of a lot of the boilerplate and setup for a task that indicates we should explore how we’re doing the task.
What I want to see is using these tools not to delegate our problem solving but finding ways to enhance and accelerate it and I don’t think writing spec sheets is the answer.
One, that sounds truly miserable.
Two, there is a decent body of evidence to suggest that this method does not actually speed up development unless you go full lights out software factory which… Why would you want to do that?
https://ide.mit.edu/insights/ai-productivity-and-roi/
EDIT: As an aside this actually reminds me of the Xerox park study into efficiency gains for keyboard heavy workflows vice mouse heavy workflows. Keyboards were perceived as faster by subjects but when actually measured the mouse was faster.
What is the difference between the models writing code “well” and their performance in this context? Are we referring to readability?
Genuine question. If we use agents to read, edit, and review code, why do we care about readability? That’s a human constraint. Unless attempting to do those three is not effective and thus requires human attention to correct issues which would justify readable code. If that’s the case; why use the agent to edit the code in the first place?
To quote the research paper conclusion…
Conclusion We evaluate the impact of context files on coding agent performance for four common coding agents on SWE-BENCH and the novel CTXBENCH, built from recent GitHub issues and less popular repositories containing developer-written context files. We find that all context files consistently increase the cost and number of steps required to complete tasks. LLM-generated context files have a marginal negative effect on task success rates, while developer-written ones provide a marginal performance gain, neither statistically significant. Our trace analyses show that instructions in context files are generally followed and lead to more test- ing and broader exploration; however, they do not function as effective repository overviews. Over- all, our results suggest that context files don’t improve coding agent performance, and should only contain specific additional instructions beyond what is already available in the codebase. This high- lights a concrete gap between current agent-developer recommendations and observed outcomes, and motivates future work on principled ways to automatically generate concise, task-relevant guid- ance for coding agents.
That sounds like “Agents.MD doesn’t work” to me.
Am I missing something?
They are which is encouraging but I find culture tends to “flow from the top”.
I fear its only a matter of time.