Infinite Ascent.

by CJ Quines • on

taste and vibecoding

now let me tell you, i’m the biggest hater

feels like it’s unavoidable to be a software engineer and not think about vibecoding in some sense. i’m a huge ai skeptic. for the past five years, the most useful i’ve found llms are for amusement purposes, like writing haiku, and i haven’t found it that useful otherwise. which, i’m glad it’s not just me, but it feels kinda bad since writing code is supposed to be something llms are good at.

my old excuse for this was something like, well, it just isn’t good at the kind of software engineering i need to do? which is, empirically:

it’s only recently that i’ve been impressed by llm output, and it was when i was rearranging a bunch of frontend components. i used claude code, gave it a few pointers of where in the code base it can look at examples for, and it kinda worked? i watched what it did, interrupted when i needed to and gave it guidance, but otherwise i wrote zero code and made a pull request and it was. fine.

that moment broke me, and kinda made me feel weird. it’s part of what was going in my head when i wrote my last post: “i don’t like how ai could grow to obviate my job.” if claude code could do a whole frontend ticket on basically its own, who’s to say it can’t do any of the other things in a few months, given the rate of progress?

so i tried using more claude code for gph work. i wrote a bunch of frontend state syncing and hooks and stuff, and i needed to write a ui for it. so i get claude code and get it to make an interface for the state, which it does, and it’s okay. again it’s a little back and forth to get the result i want, but it’s smooth.

i tried playing with it and found some bugs. and i was already in the vibecoding mode, so i thought, heck, why not keep going? i ask claude to try to fix the bug. it goes in an unrelated tangent, and i could tell it’s unrelated, but… i decided not to interrupt. it failed to fix the bug, i say so, and it makes another attempt. this time it entirely replaces some of the state syncing logic i wrote, declaring it buggy. and to be fair, it was, but the design that it chose to replace it with was less elegant. but again, decided not to interrupt.

it was still buggy. so i ask it to write unit tests, and then iterate on them, and then end-to-end tests, with a browser and everything. after two hours of iteration, which mostly consisted of me playing monster train 2 on the side, and saying a sentence or two to claude every other minute, it got the correct functionality. this is after several thousand lines of tests and changes to make things work. the next day, i decided to fix the thing myself, and after thirty minutes or so i got the right result with significantly less thrashing.

i was talking with david yu about this the other day, and we ended up talking about vibecoding. some bullets:

anyway. i still use llms for various things. not enough to say that i use use them, given the people i work around. not enough that i’m fully comfortable reaching for them. it’s still weird and it still feels kinda strange when i do so, but i’ll admit that a useful tool is useful even if it’s weird.

Comments