this post was submitted on 04 Mar 2026
70 points (93.8% liked)
Programming
25998 readers
166 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Theres a fundamental minimum amount of boilerplate you just have to write to make a functioning app, even if its simply just describing "this thing does this"
For example, if Im making a web api, theres just fundamentally a chunk of boilerplate that wires up "This http endpoint points to this domain logic over here"
And then theres gonna be some form of pre-amble of describing "it takes in this input, it returns this response, and heres all its validation"
And while its simple code, and its very simple to test, its still a buncha LOC that any half assed dev can write.
Stuff like that AI can shit out very quick given an input requirements doc that you, the dev, were gonna get anyways
And then you, the dev, can fill in the actual logic that matters after all that basic boilerplate stuff.
"Yes, it has a phone number input, its required, and it must fit the phone number regex we defined. So... shocker, you gotta put a string called PhoneNumber on the inptu model, and another shocker, its gotta have the phone number validation on it and required non empty string validation on it"
It doesnt take much trust to put into the LLM to get that sorta stuff right, but it saves me a whole bunch of time.