Article Writing

2-Jun-23 4:35

Dear Colleagues,

Still waiting for approval...

Sean Ewington2-Jun-23 5:50

Sean Ewington

2-Jun-23 5:50

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

Mirzakhmet Syzdykov2-Jun-23 6:21

2-Jun-23 6:21

Thank you, Sean

Mirzakhmet Syzdykov2-Jun-23 6:33

2-Jun-23 6:33

Just finished tip/trick, please check it

Sean Ewington2-Jun-23 6:41

Sean Ewington

2-Jun-23 6:41

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

Mirzakhmet Syzdykov2-Jun-23 6:49

2-Jun-23 6:49

Do you mean that there is no possibility to solve this question?

Sean Ewington2-Jun-23 8:07

Sean Ewington

2-Jun-23 8:07

I mean we will no longer accept your article, tip, Blog, or Project submissions on CodeProject.

Thanks,
Sean Ewington
CodeProject

Mirzakhmet Syzdykov3-Jun-23 1:56

3-Jun-23 1:56

Thanks to all, bye

Mirzakhmet Syzdykov2-Jun-23 8:01

2-Jun-23 8:01

Follow the link:

GitHub - M-S-Developers/IdahoJS: Web framework for synchronization[^]

OriginalGriff2-Jun-23 10:42

OriginalGriff

2-Jun-23 10:42

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!

Nelek2-Jun-23 11:53

Nelek

2-Jun-23 11:53

30 minutes?
The timestamps of the messages say 12 D'Oh! | :doh:

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.

OriginalGriff2-Jun-23 18:38

OriginalGriff

2-Jun-23 18:38

Long day yesterday ... math was clearly beyond me. Blush | :O

My posted articles are constantly deleted

Nelek2-Jun-23 11:52

Nelek

2-Jun-23 11:52

Really good explanation, sadly it seems he is tips-resistent Sigh | :sigh:

M.D.V.

Mirzakhmet Syzdykov1-Jun-23 22:53

1-Jun-23 22:53

Please help, I need more advise

Richard MacCutchan1-Jun-23 23:12

1-Jun-23 23:12

We have given you advice. I already suggested today that you re-read the suggestions from @RichardDeeming in his message below at Re: My tip/trick deleted 3rd time - Article Writing Discussion Boards[^]. You should also read CodeProject Article FAQ - Part 1: How to Write a Good Article for CodeProject[^].

Mirzakhmet Syzdykov1-Jun-23 23:14

1-Jun-23 23:14

I have revised and submitted, please review it

Richard MacCutchan1-Jun-23 23:27

1-Jun-23 23:27

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.

Mirzakhmet Syzdykov1-Jun-23 23:24

1-Jun-23 23:24

Thank you, just edited, please review the tip/trick

Richard MacCutchan1-Jun-23 23:28

1-Jun-23 23:28

Please stop posting, and read my suggestions above.

Mirzakhmet Syzdykov1-Jun-23 23:43

1-Jun-23 23:43

This is my entirely reviewed post, thanks

Mirzakhmet Syzdykov1-Jun-23 23:41

1-Jun-23 23:41

Thank you, just done, please check!

Richard MacCutchan1-Jun-23 23:46

1-Jun-23 23:46

You have not done anything, you are just reposting the same thing over and over. As I keep suggestiong, stop posting something that we keep telling you is not accptable for publication. Go to the links I gave you and look at examples of properly well written aricles and tips.

Mirzakhmet Syzdykov2-Jun-23 1:45

2-Jun-23 1:45

I hope this is my last post, waiting for your comments.

I have added the problem description, outcome and vice versa.

Mirzakhmet Syzdykov2-Jun-23 0:40

2-Jun-23 0:40

Just re-worked, there's no more to add for this tip/trick - it's quite clear in the sense of term framework.