|
When I copy/paste some piece of code (not a library), I always write the source link in comment. (without any other explanation)
The reason is that there is no better documentation for the snippet than from the web page I've taken it.
Indirectly I give credit to the author, but it's only because I'm too lazy to copy paste his web page in comment 
|
|
|
|
|
When I am at work and I find some code on the internet really NO ONE is going to care where I got it. In fact, I think my boss would delete it because it makes Classes and Methods a bit more harder to read (seperate the thank you's from the comments that really matter).
Our company uses DevExpress tools and also had an ExpertsExchange account. If they give us code I (or rather, my employers) have paid for it. I am most certainly not giving credit to someone who gets paid to write me code.
When I am working on an app by myself really no one is going to read it, so why should I?
When I am making an app that might be on CP (or wherever on the internet) I would probably thank the original author, but would probably do so in the post or article that comes with it, not in code.
It also depends on the content which I have copied. If its a tip or trick that is everywhere on the internet I will not give credit, if it is a really specific piece of handy code by author X that can be easily identified as original author I will give credits.
I also have to say that I rarely take literal code from the internet. It always needs some tweaking 
It's an OO world.
|
|
|
|
|
if i would ask any one of you to tell me the correct formula to live my life to the fullest,what would you tell me?
|
|
|
|
|
I would say, this is not the correct place to ask this. Go to The Lounge[^].
..Go Green..
|
|
|
|
|
I'll need to refer to the case of Finders v. Keepers.
-Lionel Hutz
|
|
|
|
|
I always believe a developer should get credit for his/her work.
I do not, however, go out of my way to put it in an about box as their header comments usually give them credit.
If I have access to source code I will change the namespace to fit into my Controls namespace for the solution.
If it is bad name for a control, I change the name of the control to something better suited to what it is.
But I leave the information untouched and all comments document who developed the code and where it came from.
I never remove that info. And I would never claim it as mine. After all -- if I did I'd get blamed for any bugs in it. 
|
|
|
|
|
* EDIT * I misread the question.. if there's a license that say we have to credit them, I don't know why you shouldn't. *EDIT*
It's kind of hard to give everyone credits.
- Thanks Dijkstra for the A* pattern I used.
- Thanks to Gang of Four for the Strategy Pattern that I've used 2 or 3 times.
- Thanks to Microsoft for C# boilerplate code
- Thanks to the jQuery dev team.. and the jQuery UI dev.
- Thanks to grid.css. It helped me a lot.
etc etc..
We write very little original code in our applications. Unless we do.
I personally, never published any real applications in the open.
|
|
|
|
|
I can't help but think that if you can't honour the terms in the license, you really shouldn't touch the code. If you're thinking of using code from another project, read the terms carefully - if you're unwilling to agree to them, walk away.
Any other approach is morally questionable, usually illegal, and disrespecting of your compatriots. I wouldn't like my code stolen (that's the correct word here), and would afford the same respect to others.
|
|
|
|
|
that way you have someone to blame 
|
|
|
|
|
Exactly :P 
|
|
|
|
|
 5.
***** Programme comme si dept soutien technique. est plein de tueurs en série et ils savent adresse de votre domicile. *****
|
|
|
|
|
then you ain't tryin'
--
You don't hire a handyman to build a house, you hire a specialist.
|
|
|
|
|
Keep that one away from the wifes ears.
Craigslist Troll: litaly@comcast.net
"I have a theory that the truth is never told during the nine-to-five hours. "
— Hunter S. Thompson
|
|
|
|
|
|
My favorite comment begins: Based on the article <<name>> by <<name>> that I found on CodeProject....
|
|
|
|
|
.....but sometimes, stuff happens.
e.g. Sometimes you get stuff from the internet that has an 8 screenful licence agreement, for convenience I often work on a copy without the guff and sometimes forget to put it back. Generally there will be a link to the original in my own header though.
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Yes,
> when ever I take code from some article or open source code.
No,
> When ever some-one suggested me or gave code on forums, or I got via search engine - code on forums.
But, I always have a 'Thank You, that was helpful' when-ever it helped me in critical time.
|
|
|
|
|
As long as there is /someone/ to credit, I think it is a moral obligation to do so rather then pass off the work as your own.
Panic, Chaos, Destruction.
My work here is done.
or "Drink. Get drunk. Fall over." - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre
Have a bit more patience with newbies. Of course some of them act dumb -- they're often *students*, for heaven's sake. -- (Terry Pratchett, alt.fan.pratchett)
|
|
|
|
|
They put the effort in, it would be rude and unethical to not credit them.
If the conditions they impose for using their work are too onerous, I look elsewhere instead.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
Depents on the term and conditions of obtaining their licence.
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >>
|
|
|
|
|
- I'm getting the same solution in many links(say 10+ links), so now what should I do? which link I should acknowledge in my posts?
- Also for an article I need to include a bunch(say 5 solutions(not code) - one small paragraph for every solution) same as above case I got same solution in many links. Is it enough mentioning acknowledgements like Thanks to Google & programming forums(asp.net, Stack overflow, bytes, eggheadcafe, daniweb, dotnetspider, etc.,)?
Appreciate your replies. Thanks in advance.
|
|
|
|
|
thatraja wrote: I'm getting the same solution in many links(say 10+ links), so now what should I do? which link I should acknowledge in my posts?
Hmm... Not always. Some code is very generic and used everywhere. In such case, you can't produce any copyright notice on them.
Suppose, some code which is not a generic one and a person implemented it for the first time. Yes, in that case it is always appreciable if you put a link or the authors name in that code (whether he publishes his own copyright or not).
Think on your own about the code and if you see it's values to put the copyright of actual author, go ahead and put it. If it is a very basic code, you don't have to think it twice.
Regards - Kunal Chowdhury | Microsoft MVP (Silverlight) | CodeProject MVP | Software Engineer
|
|
|
|
|
Kunal_Chowdhury wrote: If it is a very basic code, you don't have to think it twice.
This is enough for my doubt. Thanks Kunal.
|
|
|
|
|
I'm missing two options in the list:
- Of Course!
and
- When I remember!
Why can't I be applicable like John? - Me, April 2011
-----
Beidh ceol, caint agus craic againn - Seán Bán Breathnach
-----
Da mihi sis crustum Etruscum cum omnibus in eo!
-----
Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932
|
|
|
|
|
I agree to you.
Sometimes, we are in so hurry that we forget to credit them in our code and we never wish to ethically do so.
// ♫ 99 little bugs in the code,
// 99 bugs in the code
// We fix a bug, compile it again
// 101 little bugs in the code ♫
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
