Mastodawn

Everyone is understandably using the black-box analogy to describe the problem with vibe-coding: you don't directly write the code yourself, so how can you understand and debug it? I find this persuasive, but am trying to see all sides. Is the vibers' counter-argument that:

- you simply keep iterating until the code does precisely what you want (tests presumably becoming critical)

- it's similar to most high-level language programmers anyway: their black box is compiled machine code

Fair?

Show thread

spara Feb 24

@tomchadwin

vibe coding removes a lot of tedious stuff, so you can get straight to the business logic

if it's a black box, then you're doing it wrong

Show thread

Tom Chadwin Feb 25

@spara I don't want to misunderstand this. Are you saying that you should 100% still understand all of the generated codebase? I wonder how realistic that will be as we progress along this road.

Show thread

spara Feb 25

@tomchadwin I don't use AI to generate an entire codebase. I use it for doing tedious stuff like, "here's some sample data, generate data classes." Or "use this package to write a function that processes some data." I use it to write chunks of code that I assemble. Think of it as mise en place coding.

Show thread

Tom Chadwin Feb 25

@spara I feel a hashtag coming on. Joking aside, great, but I guess that places you outside the class of users in which I'm interested. And that's hardly surprising, given your dev career/background. Or perhaps you can see your usage spreading in scope in the future?

Show thread

spara

@tomchadwin Doubtful, I am also a firearms instructor and I treat AI the same way I treat students when I hand them a gun.