Hey, you guys! When I read the academic honesty policy, there was one part that said if you take inspiration from somebody else’s code, you need to credit them, and I wanted to ask how to do that… I was stuck on something with my CSS styling and web layout, and when I read somebody else’s code, I understood how to do it, but I didn’t know how to credit them…
you can add a comment in your code near the code you have written from that inspiration with a link to the source
1 Like
Ideally you should not be looking at someone else’s solution to the same project though. That defeats the purpose of the projects.
And yet the HELP button asks that we check other forum posts before asking a question. 
Sure, but the other forum posts have working code redacted or blurred for exactly this reason - You should not look up solutions before you have working code. You should do research and look at how other people have worked issues. You should not look at solutions others have used to pass.
Since “forum posts have working code redacted or blurred”, there shouldn’t be any solutions to look at, so problem solved. Besides, that would take all of the fun out of it, wouldn’t it? In this particular case, it sounds like @itsxxtx was able to look at someone else’s approach and learn from it. And isn’t that the goal?
1 Like
Blurred solutions still can be unblurred and read. And the forum is not the only place to find solutions.
Which is exactly why I very specifically said that its not good to look at solutions. You should not look at somebody else’s approach in their working solution to a project before you have a working solution to a project. That defeats the entire point of these projects.
Now, looking up someone else’s troubleshooting without looking at the exact solution code or looking up code for something else entirely that happens to have a similar small feature you want to understand is something I recommend.
I think we are in agreement regarding searching for someone’s solution to make your own, which would take all of the fun out of doing your own thing.
But back to the HELP button…of course someone would be looking for an answer to help them move on and that should not be an issue, imho. Again, it can be part of the learning process. And I’ve seen a few approaches that I found interesting to play with, one that I thought was cool actually didn’t work when I tested it…ah…but I digress. 
1 Like
Yeah, once you have working code you should totally go look up different approaches. Before that point, when I’m helping someone I try to give them the smallest nudge they need so that they get to be the hero and get the win themselves with their own debugging.
1 Like
That’s a skill I haven’t yet fully mastered, but I’m working on it.
That’s not what I did, I want “looking at someone else’s solution to the same project”… I was asking questions about a problem I was facing then I was sent an example of how similar problems could be solved in an imaginary scenario and I just took the general idea of how to solve my problem.
No worries. I clarified exactly because some people do go look at solutions and it’s a bad idea.