this post was submitted on 05 Aug 2026
47 points (100.0% liked)

Programming

28032 readers
718 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] tatterdemalion@programming.dev 0 points 2 days ago* (last edited 2 days ago) (1 children)

Not always. Prototyping can be valuable in many circumstances when you don't know the shape you'd like the code to take. Sometimes you need to try something before you know if it's right. I'd rather throw away prototype code written by an LLM than code I had to write the hard way.

[–] spartanatreyu@programming.dev 1 points 1 hour ago

Not always.

Yes always. To paraphrase Feynmann: What you did not create, you have not understood.

Prototyping can be valuable in many circumstances when you don’t know the shape you’d like the code to take.

Yes

Sometimes you need to try something before you know if it’s right.

Yes

I’d rather throw away prototype code written by an LLM than code I had to write the hard way.

No.

If you consider writing your own code "the hard way", then your goal should be becoming better at prototyping yourself. It's a skill that you need to requires purposeful effort to strengthen. But once you have it, you get both the understanding behind the code and the prototype.