pull down to refresh

139 sats \ 2 replies \ @optimism 21h \ parent \ on: The Cult Of Vibe Coding Is Insane AI devs
  • I like 5..
  • I think that 1. and 4. are contextual / specific to job-at-hand and could objective-poison generic functioning and degrade.
  • 2. and 3. are subjective, but valid.
  • 6. I would personally not do because rework is expensive. I'd rather "1-shot" (after planning / analysis / exploration) an implementation and throw it away than have a bot rework stuff. Arguably, latest releases did get better at rework, but I'm still feeling as if it is more costly.
write
compose
85 sats \ 1 reply \ @k00b OP 20h

I agree with your assessment of the rules. They are my personal generic rules absent bots - context is usually something relatively frivolous where human readability takes precedence over nearly everything. I find rework from a checkpoint created by these rules easier than going in the other direction.

reply
139 sats \ 0 replies \ @optimism 20h

I guess rework from checkpoint also means redo, rather than rework. (The checkpoints were broken when combined with having full control cmdline git in the early days, so I hated that feature most of all)

reply