3 ms·

> In the last week i've vibe-code (vibe-engineered?) a typescript project with 230+ commits, 64 typescripts files, with 27k+ lines of code. Too much to actually

by smsm42 1y ago

> In the last week i've vibe-code (vibe-engineered?) a typescript project with 230+ commits, 64 typescripts files, with 27k+ lines of code. Too much to actually read. Congratulations, you discovered that generating code is only part of software development process. If you don't understand what the code is actually doing, good luck maintaining it. If it's never reviewed, how do you know these tests even test anything? Because they say "test passed"? I can write you a script that prints "test passed" a billion times - would you believe it is a billion unit tests? If you didn't review them, you don't have tests. You have a pile of code that looks like tests. And "it takes too long to review" is not an excuse - it's like saying "it's too hard to make a car, so I just took a cardboard box, wrote FERRARI on it and sit inside it making car noises". Fine, but it's not a car. It's just pretending. If it's not properly verified, what you have is not tests, it's just pretending.

ako 1y ago
I’m well aware, thank you, have been coding for 40+ years (including 6502 and 68000 assembly), masters in computer science, have built healthcare software where bugs can lead to death. But with LLMs enabling us to generate source code faster, our review process is becoming an increasingly larger bottleneck for productivity. We need to start thinking how we can scale this process.
- smsm42 1y ago
  It's as much bottleneck for productivity as cars being made of metal are bottleneck for speed. Sure, you can make a paper car. It probably would be faster. Until you collide with something and then you discover why the metal frame was a good idea. If you generate code that you can not verify or test, sure, it's faster. Until something goes wrong.
  - ako 1y ago
    That is why formula 1 race cars are mostly carbon fiber, including the frame. They identified the bottleneck, and replaced it with a better solution...
    - smsm42 1y ago
      Better solution for a race car, driven on specialized tracks, by highly seasoned professional, who is paid enormous money, in compensation for the grave risks he is taking. It's not a better solution for everyday car driven by everyday person. Most race cars aren't even street legal, and getting arrested for driving one on the street would be the best outcome. Getting seriously hurt would be most likely.

by smsm42 1y ago

ako 1y ago

I’m well aware, thank you, have been coding for 40+ years (including 6502 and 68000 assembly), masters in computer science, have built healthcare software where bugs can lead to death. But with LLMs enabling us to generate source code faster, our review process is becoming an increasingly larger bottleneck for productivity. We need to start thinking how we can scale this process.

smsm42 1y ago
It's as much bottleneck for productivity as cars being made of metal are bottleneck for speed. Sure, you can make a paper car. It probably would be faster. Until you collide with something and then you discover why the metal frame was a good idea. If you generate code that you can not verify or test, sure, it's faster. Until something goes wrong.
- ako 1y ago
  That is why formula 1 race cars are mostly carbon fiber, including the frame. They identified the bottleneck, and replaced it with a better solution...
  - smsm42 1y ago
    Better solution for a race car, driven on specialized tracks, by highly seasoned professional, who is paid enormous money, in compensation for the grave risks he is taking. It's not a better solution for everyday car driven by everyday person. Most race cars aren't even street legal, and getting arrested for driving one on the street would be the best outcome. Getting seriously hurt would be most likely.