Okay, I got two questions and I never seem to get satisfactory answers but I'm actually curious.
1) What kind of code are you writing that's mostly boilerplate?
2) Why are you writing code that's mostly boilerplate and not code that generalizes boilerplate? (read: I'm lazy. If I'm typing the same things a lot I'm writing a script instead)
I'd think maybe the difference is in what we program but I see say similar things to you that program the types of things I program so idk
I could probably be using the word boilerplate wrong, but to me, it's anything that isn't logic. So anything with basic interfaces, interacting with databases, etc is boilerplate. It's not literally the same code every time, but it's the parts of code that I don't have to make a map of how it should work.
E.g. I write financial modeling software, designing the interface, getting data from APIs, pulling transactions from database is all boilerplate. I can write in plain English how that should be done, for me to do it, is to just look up the exact methods / structures / etc. AI can do that pretty well... sometimes.
The hard part is figuring out how to make that information meaningful and take action on it, display it to the user, and make certain there aren't mistakes in the interaction of the previously mentioned areas.
1) What kind of code are you writing that's mostly boilerplate?
2) Why are you writing code that's mostly boilerplate and not code that generalizes boilerplate? (read: I'm lazy. If I'm typing the same things a lot I'm writing a script instead)
I'd think maybe the difference is in what we program but I see say similar things to you that program the types of things I program so idk