I'm constantly surprised by developers who like LLMs because "it's great for boiler plate". Why on earth were you wasting your time writing boiler plate before? These people are supposed to be programmers. Write code to generate the boiler plate or get abstract it away.
I suppose the path of least resistance is to ignore the complexity, let the LLM deal with it, instead of stepping back and questioning why the complexity is even there.
> Write code to generate the boiler plate or get abstract it away.
That doesn’t make any sense. I want to consider what you’re saying here but I can’t relate to this idea at all. Every project has boilerplate. It gets written once. I don’t know what code you’d write to generate that boilerplate that would be less effort than writing the boilerplate itself…
>Every project has boilerplate. It gets written once.
Agree with you - I think when my colleagues have talked about boilerplate they really mean two kinds of boilerplate: code written once for project setup, like you describe, and then repetitive code. And in the context of LLMs, they talking about repetitive code.
I'm constantly surprised by developers who like LLMs because "it's great for boiler plate". Why on earth were you wasting your time writing boiler plate before? These people are supposed to be programmers. Write code to generate the boiler plate or get abstract it away.
I suppose the path of least resistance is to ignore the complexity, let the LLM deal with it, instead of stepping back and questioning why the complexity is even there.