11 AnswersNew Answer
Sir, modules are usually built on hundreds of lines of code. Would you like to reinvent the wheel? Or just use an existing solution that is standard
By the same logic using programming languages in the first place is cheating. Only coding in binary is honest work -- and only when done on a computer you developed and built yourself. (You can extend this line of reasoning much much further if the absurdity isn't obvious yet.)
Hey Simon Sauter, how low do you want to go, mining the silicon to make the transistors, if they even use silicon anymore? 🤣
It's only cheating when you don't cite the original authors and pretend it is your own work. Especially when you plan to make money by an app using someone else's module, you must check whether it is proprietary or open source or cc or whatever licenses there may be...
Richard once you're skilled enough (and can spare the time) you can "give back" by helping in the development and maintenance of modules or by writing your own modules and making them available to others.
If I'm doing a problem in a textbook, I will do a lot of the code myself. However, if I'm doing a problem on a website or something that's not a textbook problem, I will try to use as many "tools" as I possibly can.
First they'll have to fashion tools from sticks and stones.
If you are on a survival hike and use matches to make fire, that is cheating. If you are in your garden and use matches to light up the barbeque, it is not cheating. So if it is cheating or not is a matter of perspective, goals and situation.
Yeah it is cheating if you want to learn stuff. But not if you know the logic that's used in those modules. If you don't, then you have to learn it before using a module, or try to build it from scratch. But none of the above is clever if you concentrate of building than learning. Then you can use any resource you want, you don't need to know how it works
They are shortcuts