4 ms·
I'd push back on your characterization of "fictitious" here, since all you're asking them to do is "document" their work. From a software engineer's perspectiv
by diminoten 7y ago
I'd push back on your characterization of "fictitious" here, since all you're asking them to do is "document" their work.
From a software engineer's perspective, that's all I really want/need to do for my colleagues. I don't need to "show my work" because they're making sure I didn't copy/paste, they're trying to move quickly and don't have time to work things out on their own about how I came up with the solution.
Maybe "show your work" should be taught; less because it's a gateway into the mind of the solution provider, and more because it's helpful to others to see how someone arrived at a conclusion.
- gaspoweredcat 7y agoi dont really think anyone cares if somethings been copy/pasted as long as it works as it should, the most talented engineer i ever met told me theres no need to be ashamed of it, theres no point reinventing the wheel if you dont have to, and he was right if youve been able to adapt something else to your task then evidently you understand what it does. lets say youre building a car, maybe you take the engine from a ford and mount it on the chassis of renault with nissan steering, just because you didnt design those parts from the ground up doesnt make the end result any less valid as a final product (obviously thats a very loose analogy but you get the picture) software is a bit different though, rather than showing that you followed a rigorous formula its about letting people know how the formula you came up with works
- diminoten 7y agoI care deeply if something has been copy/pasted, but not for attribution reasons. I need to be certain the person who copy/pasted the code actually understands what the code does, rather than blindly grabbing the first result off of SO and exposing the codebase to vulnerabilities.