User avatar
Ariadne Conill 🐰therian @ariadne@treehouse.systems
5d
a friend of mine who has been experimenting with so-called 'vibe coding' walked me through what he actually is doing. and it's not actually what i expected.

but i am told that most 'vibe coders' do not use highly-structured design documents and written proofs as the initial input into the pipeline
7
1
2
0
User avatar
Ariadne Conill 🐰therian @ariadne@treehouse.systems
5d
i don't think i would want to write software that way, since i'm more of an experiential type of person, but i think i can at least understand it now
1
0
2
0
User avatar
Ariadne Conill 🐰therian @ariadne@treehouse.systems
5d
he thinks source code itself will be meaningless soon, i'm not sure if he means the code itself will be incomprehensible (i believe it) or that the specs and proofs become the effective source code

probably both, i guess
6
0
2
0
User avatar
gaytabase @dysfun@treehouse.systems
5d
@ariadne does he still check the generated code? he won't forever.

the belief is that you just update your requirements and let the machine figure out how to make it happen. it's just a new version of "the prompt is the code"
1
0
2
0
User avatar
Ariadne Conill 🐰therian @ariadne@treehouse.systems
5d
@dysfun yes, i think that is the point he is making. by 'soon', he means within a few years, not like next month or whatever.
2
0
1
0
User avatar
gaytabase @dysfun@treehouse.systems
5d
@ariadne if you hadn't noticed a worrying trend, an awful lot of CEOs now believe that agents will find and fix bugs so quickly that it's okay to push bugs straight to live. and that if they aren't doing it now, they will soon.

this is the slippery slope he's on. the next step is to stop checking the output.
1
0
2
0
User avatar
illy [Shrimple-mode] protomoji_orange_flag_lesbian @illyBytes@shrimp.imsofucking.gay
5d
@dysfun @ariadne New Jersey programing philosophy taken to the extreme lol
0
0
4
0