The answer, as with everything in software development, is that it depends.
A god method with 100 optional params that is usually bad practice. But a common pattern is to allow for an options object to be passed, and that object may contain 0-n supported parameters. This pattern is used everywhere, see graphql as a widely used library that is based on this.
One click install that provides regional VPN, multi-index torrent searching, scheduling, auto downloading based on simple criteria, and then file and metadata management.
I do all this now with various apps, but a single package that does everything that I could install on a new machine and start downloading immediately.
Exact same thing happened to me. Group project needed a programmer, I was a gamer with a nice computer so I volunteered. 15 years later and I’m a software engineer at a huge company.
I’ve never heard of WET, but that is exactly the process I preach to my team. Refactor only once the same code block is used 3+ times as that tends to define a method that is a utility and not business logic specific.
It is absolutely not theft. If you’d like a physical crime to compare it to, forgery would be what you are looking for. But piracy is not at all theft.
That is, unless you are talking about Captain Davy Jones and his pirate ship. That type of piracy is theft.
Simple answer, unit tests.