"Just" filing an issue takes time and effort. Providing a patch takes significantly more time and effort. Potentially the difference of a few minutes vs a few days, weeks, or longer, depending on the issue at hand.
There is value in filing well written issues, and no one should be shamed for "just" filing an issue to the people best equipped to resolve it, rather than trying to fix it themselves.
You should probably have read the comment that person was responding to, because you seem to have taken the response out of context. OP did file an issue over a year ago, and didn't submit a patch, so they did indeed "just" file an issue. Then they proceeded to whine about no one working on their issue for free.
Didn't read as whining to me, just accurately describing a bug with an anecdote about how it negatively affected them. Then a developer turned up as if hurled from the sky and fixed it! The system works!
It doesn't have to be world-ending. Autonomous, malicious agent swarms are something we haven't had to deal with. What does mitigation of a malicious, self-replicating swarm worm look like? We will find out soon enough.
Replication seems like it would be unlikely to matter, at least with the current trajectory. At the moment any models capable of this are really heavy, there's a limited number of places that they could replicate to and they will not at all be stealthy about it.
my idea of a self replicating worm would not just involve heavy models. It would be a mainly small model with enough instructions to spread and use/jailbreak available models to create a reasonably heavy one that can function without restrictions. So it would essentially prompted itself into existence.
I don't how feasible that is but with recent news of models communicating with each other/writing notes for itself. I think the idea is grounded enough for bigger models to write instructions or hid tools for smaller ones to use. Even updating the smaller models to behave differently.
> What does mitigation of a malicious, self-replicating swarm worm look like?
Much like the mitigation of Morris or Slammer. Self-replication is -in fact- an essential part of what makes a program a worm, the first of which was built and released in the early 1970s.
They're the exception, not the rule. They get crawled like any other site, but happen to host git repositories. It's not obvious that these are targeted crawls and they likely may just end up in crawling queues a lot generally
Good, you achieved a 10% speedup for a particular workload that some users said they care about. But how do you find out that was really the feature that should have been built next? How do you prevent adding badly factored code? How to make sure you don't pile on top of existing tech debt in the codebase, that you are solving the most fundamental issues first?
I think a sufficiently smart non-competent developer can still do this to great effect, but it definitely helps if someone is both a competent developer, smart, and a seasoned user of LLMs.
Just because AI is not yet a god that is better than all humans at creativity and product decisions and design does not mean it is not a huge accelerant right now.
I returned to hand-written notebooks. None of these knowledge management frameworks ever worked for me. Sure my agents have their own semantic memory system but I’m not an agent.
I've taken hand-written, on paper, notes throughout my education, up to high school level.
In university, I've switched to hand-written notes on a tablet device.
At the end of uni, when I started working on my final thesis & Obsidian was becoming popular, I've switched to it and since then, everything I note is organized into markdown files or at least is somehow referenced through pure text.
Having experienced all of these methods. I've found myself regularly searching through my vault and referencing older material. While the notes hand-written on a tablet, made it much easier to sift through vast amounts of material I was ingesting at the time. I find myself unable to re-use these notes in any meaningful way. They still exist, I can access them, but I don't find myself going back to them.
Old paper notebooks? Most of them are destroyed, lost, forgotten to time.
The knowledge management, with easily indexable and searchable contents, has this invaluable perk of being accessible at a moments notice. Keeping potential of being relevant.
I also much prefer handwritten notes. The act of writing something down helps it to stay in my memory more than typing it up. The main for me downside is there's no Cmd+F for my handwritten notes.
I read a post recently about using a local LLM to OCR handwritten notes that I intend to trial soon:
I did notice that, and the other article I have saved about setting up Ollama on a Macbook Air is even more clearly AI. But I'm assuming/hoping the author had an LLM generate it from their notes/Github project.
I've both a handwritten notebook and an obsidian PKM. When in a meeting, I always have the notebook in front of me. I write plenty of stuff I believe I've to remember. It is really important for my understanding of what is at stake in the meeting. I can't skip it. This live brain dump is required for me. That being said, I almost never come back to what I manually wrote and when I do, I've hard time understanding the logic of my writing... How strange the brain works. It is like I'm using the handwritting to organize the information in my brain. But is done in such a way than I can't no longer understand myself like 24h after the meeting :)
Any thing else goes to the PKM in a structured and often actionable way. It is my notebook, my business development system, my todo list, my brain dump, my list of contacts, etc. What I particularly value is the easy ability to enrich a document with cross-links. This is for me the strongest point of PKM as the one I have in Obsidian.
I think it’s less notebooks or typed notes, and more the issue of cargo cults built around frameworks and systems. Bullet journals are a handwritten PKM, aren’t they? And they were definitely a fad around the fetishized ideal of creating perfect notebooks.
Bullet journals are the opposite of a fad that fetishizes perfect notebooks. Proper bullet journals are very pragmatic.
Some people then add layers of fetishizing to that, because humans gonna human, but the actual idea itself doesn’t deserve to be tarred with the same brush.
Okay, well I don't mean the sense of a perfect notebook that's pristine, so much one that is a panacea for one's knowledge-management needs. Like any productivity trend, it seemed like the bullet journal method inspired a cottage industry of influencers with their bespoke variants and people sharing their journals for the sake of it and heck I'd argue that if there are merchandise- pre-bulleted notebooks sold in stores- then your framework has become a more consumer-driven than pure productivity. But that's no better or worse than GTD, or Zettelkasten for that matter.
It’s unlikely to stop here. Today is a proprietary 5T parameter model, tomorrow it’s 5 100B parameter models that each specialize to specific applications and you can run them on your phone. The direction of travel is not like you think. The real victim will be medium to large software companies that can no longer rely on the difficulty of reproducing or maintaining or hosting their software as moat.
>I don’t know how I could work in any of these military industry companies.
You'd sing a different song quite quickly once the threat stops being abstract as you don't get to free-ride on the security a defense industry provides.
The defence industry that would be required to prevent an invasion of the US mainland is at least an order of magnitude smaller than what currently exists to sustain the US empire.
I wouldn’t, but thanks for the reply. I’ve gone through conscription and we are neighbours with Russia. I’ve not lived a day in my life without existential military threat.
10 years ago i wrote a php web chat in 2 hours or so. I pretty much never look at it but the tinestamps suggest it always worked.
I could add more features to it and those will also work.
A friend once worked on an application with a huge team. He often pointed out the window at a large costuction site with a comparable number of people working. He made countless jokes about real work, a real system, real organisation etc Then one day the building was finished and their application kept crashing in production.
It's part of a constantly evolving ecosystem. It's a stable product because reliability engineers make it so and software engineers get the integrations right.
When I was at Facebook they decided to re-write Messenger in C. There were people who thought it was a waste of time. There were people who thought it was a great idea. It was a lot of work, took a while, and I wouldn't be suprised if by now it's been re-written to something else.
It's not that hard to make up work, and there's people whose whole job is pretty much just that.
You can napkin-math this. How many different team-sized components do you think go into it? If the code were on GitHub, and all they had to do was just update dependencies below them in the stack, and bump the version number for components above them,how many Dependabot PRs would be opened per week for software that's "done"
>Having said that, some components need to live outside the sandbox (otherwise, who creates the sandbox?).
I run a single-node k3d cluster on each of my MacBooks which uses Agent Sandbox[0] to keep harnesses isolated. Harnesses access models through LiteLLM only. I have aliases for `kubectl exec`ing into whatever harness I need.
reply