If the collective comprehension and articulation of a concept is flawed, and our individual comprehension is flawed, then we cannot expect AI to be any less flawed than the material it has to work with.
This seems to be at the heart of much of the debate in AI augmented coding.
Mutation testing is a method that's becoming increasingly important with AI-augmented coding. Without it, we could risk future bugs in our agent-written code, even if what we release today seems to work.
Read on: https://ideas.riverglide.com/mutants-in-the-machine-the-ai-illusion-of-test-driven-code-37d623642486
I recently joined Jack Hannah for a chat on @tuple's "Distributed" podcast.
We talk about what distinguishes teams at the 'Elite' benchmark of DORA's Software Delivery Performance metrics and how AI is reshaping software delivery.
We also explore what return-to-office mandates often miss about remote collaboration.
I also give shout outs to @jasongorman , @kevlin and @davefarley77
Maybe we'll see them on the podcast in future? 😉
Watch here:
https://youtu.be/y7KZd6x7-lo
(55mins)
@range_marten I cannot say, however, I can speculate that people may want to containerise it in their own ways suited to their environments.
They do provide links to a reference container that you can use.
I've said this before, please use a container for your AI coding assistant(s)! It's not just about what it can do to your filesystem...
I've spoken to so many devs this week who aren't using a container!
Remember, it can also access all of your environment variables. API keys? Other secrets?
And then there's Slopsquatting, before you know it, you've got malware installed.
In a container, the blast radius is limited.
@PeterSommerlad @kevlin I did consider including that as another example, but felt it distracted from the key message.
And, as you know, Royce highlighted under the image I showed that the process "was risky and invites failure" because of the need for iteration.
And highlighted that iterations aren't limited just to the previous steps.
And he solved the problem of these iterative loops with the cheapest medium available at the time... paper documents.
That's a whole other talk.
@JeffGrigg @kevlin I think that is an example of exploiting a vulnerability of the Early Majority. I don't think it was a cause, but more a catalyst.
Once the chain reaction of misinformation started, it became self sustaining and accelerated thanks to its exponential spread through word-of-mouth at scale.
Many of the misinformed folks I've spoken to haven't been anywhere near any big consultants, but they learned what they know from colleagues.
