|
Yes, it is fixed now. A funny thing, all looked fine in Preview, but later there were problems.
|
|
|
|
|
I attended Machine Learning Conference, so if I write about my general impressions from the conference, without any code, would that be a topic of interest for this site?
|
|
|
|
|
Because of your excellent articles I want to say yes, but unfortunately that's not really within our editorial guidelines for the site.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Why not?
There have been a bunch of "books impressions", opinions about i.e. interviews, how work should be... and other stuff.
This would be a nice diversion, and very probably more qualitative than most of those I have said
Additionally... if he could write it as a blog and import... why shouldn't be able to write directly about it?
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Unless Chris was writing it, for as long as I've been here we don't post conference impressions. If I saw a conference impression imported through a blog, I would remove it.
I certainly see the potential value in the content, but it opens the floor to less talented authors impressions of conferences that share no real value, or worse, marketers looking for a free lunch, pointing at existing conference impressions and saying, "this one is allowed, so my self-promotional conference impression must be too."
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
I understand the point, but then we should clean up a lot of more stuff. As impressions of a book, impressions of what a good interview is...
And there were quite a few that went through.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Book impressions / excepts were allowed and encouraged at one point. It's been years since we've posted one, or since I've been reached out to to post them, though I did see at least one member post one within the last five years. I never did make an official stance about interview articles because the community hated them so much they downvoted them to hell or closed them. I tell any authors that post interview content that they are not going to be well received, and remove them. At some point I'll confer with the team about going back in time and removing these kinds of articles, but it's not an immediate concern.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Either all or none, at least consequent. That was my point.
I didn't realize how long back my memory of those was going, usually I forgot "non critical stuff" very fast  
Now that you mention it (and I really thing about it)... yes, it has been a while since the last one I remember.
Point cleared, all good and my apologies for the brain-fog 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Dear Colleagues,
Still waiting for approval...
|
|
|
|
|
I can see the other members are really trying to help you and I can see that you're attempting to make changes, but ultimately your changes are small and not enough.
If you please, let's try a different exercise here. For this article only, let's change the goal. The goal is not to get the article published. The goal, for now, is to get better at writing an article for CodeProject. Think of it that way.
Throw your existing article completely out. Start over from scratch. The first step that might be helpful is to make a rule for yourself. Write more words than code. Put it into a word counter if you have to. Write out what the code does, rather than show it.
Also, truly look at the following article by one of our top authors. Don't skim over it, don't skim over this message. Read every word. Think about it. Think about this author's approach in how it differs from your own. CodeProject readers are primarily looking for meaty, exhaustively explained solutions to their development problems, or articles that can teach them something to make their developing faster, more efficient, or expand their repertoire.
Here’s an article from one of our top authors:
HTML5 WebWorkers Experiment[^]
His primary goal is to demonstrate “Using HTML5 WebWorkers and a custom jQuery plug-in to create a Flickr image wall.” He treats the reader like a beginner. He defines jQuery, explains what WebWorkers are, then gets into why he wanted to create a jQuery plugin. Each progressive section of the article expands on his topic, thoroughly explains the code, explains the limitations he chose in his scope, discusses how each element to his plug-in works, provides numerous code examples, and most importantly, gives a source code download at the top for the reader should they need it.
Every time the community considers whether or not to approve an article, this is the style of article they have in mind. They love it, they want it, and they praise the authors enormously when they get it (and we want authors to feel like their hard work is appreciated).
If you can fundamentally change your thinking here, and you can fundamentally change your approach, we're happy to continue working with you. There's no short cut to getting an article published. Put in the time, make the effort. Take a week or longer.
If you come back with minimal changes, that's the end of the road. I don't think you're right for CodeProject. We won't consider any more of your future articles. And that's OK. Some people and institutions don't fit together. But we could. You just have to decide to put in the work.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
Just finished tip/trick, please check it
|
|
|
|
|
I appreciate you being willing to start over. But this is essentially tool sharing, which contradicts everything I tried to carefully outline in my previous message. I'm afraid we will be rejecting this tip, and will no longer accept your article submissions on CodeProject.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Do you mean that there is no possibility to solve this question?
|
|
|
|
|
I mean we will no longer accept your article, tip, Blog, or Project submissions on CodeProject.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
|
Quote: Put in the time, make the effort. Take a week or longer.
Quote: Thank you
... 30 minutes later ...
Quote: Finished!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
30 minutes?
The timestamps of the messages say 12 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Long day yesterday ... math was clearly beyond me.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Really good explanation, sadly it seems he is tips-resistent 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Please help, I need more advise
|
|
|
|
|
|
I have revised and submitted, please review it
|
|
|
|
|
Sorry, but that is still not acceptable. There is no description of what actual problem this will help to solve. Two blocks of code with no details of what the code does, where it should be placed, or why. Please go to the links I gave you and read them carefully, in order to understand what an article or tip should contain. If you want further ideas then read some of the articles post by @RichardDeeming, @OriginalGriff. And here is another example of what a well written example looks like FMBomb - A Beginner's Approach to Hardware Programming[^]. And you do not need to be an electronics expert to understand the structure of the article. So stop rushing to post every few lines of code that you write, and think carefully about what you want to say.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
