| ▲ | satvikpendem 18 hours ago | |||||||
You need to make sure the text you're typing actually compiles into a working program, so there is some degree of focus required. Compare that with vibe coding, just type a sentence of what you want and it does everything itself with no continued focus from you. The degree is completely different. | ||||||||
| ▲ | watwut 9 hours ago | parent [-] | |||||||
I did worked in teams that produced crap. They were initially all able to proceed much faster then teams that did not produced crap. They felt like being super productive the whole time, cranking out issues one after another. The initial speed slowed down after 2-3 months, but they did not noticed it. They ended up being actually slower, customers were unhappy because they were not getting functional software they wanted and the team believed themselves to be victims. The overall results, if you joined them later was "wow this is slow, you are producing crap and customer is entirely correct when they complain". My point here is that "don't care about quality" does a lot in that claim. It leads to a lot of useless and contra-productive work - you would be better off if they have done nothing. And I think what people are reproducing that state here, just faster. | ||||||||
| ||||||||