> There was one where everyone made a big fuss about such things in code reviews. There's always dumb morons... sigh. Even if you don't copy code from SO, it

> There was one where everyone made a big fuss about such things in code reviews. There's always dumb morons... sigh. Even if you don't copy code from SO, it still makes sense to link to it if there is a decent explanation on whatever problem you were facing. When I write code and I hit some issue - particularly if it's some sort of weird ass edge case - I always leave a link to SO, and if it's something that's also known upstream but not fixed yet (common if you use niche stuff), I'll also leave a TODO comment linking to the upstream issue. Code should not just be code, it should also be a document of knowledge and learning to your next fellow coder who touches the code. (This also means: FFS do not just link stackoverflow in the git commit history. No one is looking there years later)