|
Nagy Vilmos wrote: I really do need to work more
What? You tired of being a kepted man? 
|
|
|
|
|
Nagy Vilmos wrote: That means I'd confused tomorrow with today so I can go t'pub tomorrow!
You know, these updates make me really glad I get to trudge into Scumberland every day to go to work.
We need a bitter emoticon, and by bitter I mean like this[^] not this[^]
|
|
|
|
|
![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif)
speramus in juniperus
|
|
|
|
|
Damn you!!!!!!! 
|
|
|
|
|
I just posted a lengthy blog about web development (the first ever on web development too!!) on my blog[^]!!!
It's about KnockoutJS[^], WebAPI[^], T4 Template[^], etc..
And also, I have registered my blog with CodeProject, so it should eventually appear here!
But I have noticed that blog article have less exposure.. 
So should I make an article out of it? Is it much work? (I used Windows Live Writer to edit the blog entry)
I know the answer should be yes, but my hesitation is the amount of work it will take...
|
|
|
|
|
And posting something that appeared on your blog as article is a no-no (Except you really polish it up well).
|
|
|
|
|
I guess that answers it...
|
|
|
|
|
I think you were given incorrect info. See my other reply.
|
|
|
|
|
I said that not quite accurate: You'll need to refer the blog article - Also the article needs sample source code and an explanation to it. See my other answer to Dave.
|
|
|
|
|
I don't think that is correct. I checked the Submission Guidelines (http://www.codeproject.com/info/Submit.aspx[^]) and I don't see any such prohibition.
In fact, it says the below.
"Submitting code already posted at another site
You are more than welcome to submit code that is already published at another site, provided you own the copyright on that article, and provided you have not given the other site exclusive rights to your article."
So if you posted something on your blog and want to submit it as an article it sounds like its OK according to the above.
|
|
|
|
|
I didn't say that it is completely forbidden.
What I wanted to point out is that if you post an article on CP and someone finds the blog you have originally posted it the article is easily closed as plagiarization, if the blog entry was posted under a different name than your CP username - You gotta take care, some members have their finger on the report trigger.
|
|
|
|
|
haha, it's not plagiarization if I'm the author of both post!!! ^^
|
|
|
|
|
You said, "posting something that appeared on your blog as article is a no-no". I was just replying to that. I understand what you're saying though, someone could mistakenly think its plagiarized. But I don't think its a "no-no" to do what he's asking since he's the author of both.
|
|
|
|
|
Dave Calkins wrote: You said, "posting something that appeared on your blog as article is a no-no"
I was going on from the typical blog post, which is, in most of the cases, more formatted like a Tip, without a really in-depth description. It usually presents one, or a little number of code snippets.
I understand that you were replying to my OP, which was indeed unclear. I hope I was able to clarify my thoughts a bit.
|
|
|
|
|
If you make it an article and post it at CP, it might help some lowly C++ developers (like me) who are wanting to start with web development.
Don't listen to anyone who's discouraging you.
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
Rajesh R Subramanian wrote: If you make it an article and post it at CP, it might help some lowly C++ developers (like me) who are wanting to start with web development.
Check this one[^] by Sean.
|
|
|
|
|
Thank you, I appreciate the help.
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
|
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
Rajesh R Subramanian wrote: Don't listen to anyone who's discouraging you.
I'd agree with that, but it is also good to listen to advice that wasn't meant to be discouraging, just a warning.
In this case, it is OK to post a near copy of a blog, but have a good reason and fully disclose the blog you are basing the article on. That would be a link to the blog, disclose that the author of the article also wrote the blog, and the author can cover the subject in more detail with better code examples in an article. (CodeProject doesn't condone plagiarism, you need to disclose work you use to create your new work based on it. In one case I said I used logic I'd read about 20 years earlier. I said I'd added modifications to make it work better. Somebody pointed out an article on quicksort that stated one of the original methods exactly matched what I'd read, but the recommended way exactly matched my modification of the original method. So neither of us plagiarized the other, we both used common sense to come up with a better solution. The other just published it, so he is the author.)
The reason given works even when the blog author isn't the same, just disclose that as well.
Everyone sometimes doesn't say exactly what they meant and it comes across in a negative way. Just try to understand what really was meant. (I wish I always followed that advice.)
|
|
|
|
|
After reading your reply, I am not sure if you're aware of the fact that in this case the OP *is* the author of the blog.
He just wants to know if it's a good idea to write the same thing here at CP, which I said is a good idea because it will more visibility, and could help some people.
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
Rajesh R Subramanian wrote: I am not sure if you're aware of the fact that in this case the OP *is* the author of the blog.
I did say "disclose that the author of the article also wrote the blog" That really isn't a CP requirement, just something that is in the interest of full disclosure and providing an explanation of why the same thing is written in two places. (Not, look at me, I wrote this! More, I am adding value by...)
|
|
|
|
|
I agree with that point.
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
If you do the proper references... there shouldn't be a problem. 
I believe you might have to rethink it because of the reason you want to do it.
There are no secrets to success. It is the result of preparation, hard work, and learning from failure. Colin Powell
|
|
|
|
|
Why worry about exposure?
I think everybody arrives to places via google, so if there's a good match between what they've searched for and what you've written they should be able to find it.
Regards,
Rob Philpott.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
