No matter what you work on, programming is one of:
Check the documentation for a library, copy&paste the interface call, fill in the blanks.
Pick the best algorithm for the case at hand, copy&paste, change a few variable names.
Get out your snippets archive, copy&paste the one you need.
Write some boilerplate, copy&paste over and over, then fill in the blanks.
Look up how someone else solved your problem, replicate it in a way that doesn’t look like copy&paste.
Once in a blue moon, come up against an actually novel problem, spend some days figuring out the best way to solve it… then copy&paste the solution back into the project.
Doesn’t matter what you’re working on, in the end it’s mostly copy&paste 😂
I work on compilers (we can’t/don’t even have access to the C++ standard library in my case)… Most of the time, Google can’t help me ⚰️😅
It was definitely a bit more copy and paste when I was working on web applications… But even then, most of the code I was writing was fairly novel / more application and database architecture problems than trying tying libraries together.
I don’t know what y’all are working on but these comments always scare me …
No matter what you work on, programming is one of:
Doesn’t matter what you’re working on, in the end it’s mostly copy&paste 😂
I work on compilers (we can’t/don’t even have access to the C++ standard library in my case)… Most of the time, Google can’t help me ⚰️😅
It was definitely a bit more copy and paste when I was working on web applications… But even then, most of the code I was writing was fairly novel / more application and database architecture problems than trying tying libraries together.