|
OK. I got the message.
I'm normally used to continually reviewing my work (re-editing). Now, how can I understand that I'm 're-editing' a little too much? (from the point of view of CodeProject.)
|
|
|
|
|
If it is a legitime edit... there is no problem. We can follow the changes.
I remember a guy did that one edit a week, just to change a letter, add a coma or similar really small things... that's more in the way I meant.
If you really want to improve your content and the changes are needed... that's not that bad.
On the other hand... if your project is not that mature yet that need continous editing... would it not be better to finish it and then publish when you say "now is good"?
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.
|
|
|
|
|
Some authors are like this, which is fine. Just make sure you're making significant changes to the article each time. If you can't state in a sentence what changes you've made to the article, then you haven't changed enough and it might be best to combine updates.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
First, awesome that your project is getting attention! Nice one.
Second, no, no policy. It's just the ebb and flow of content.
cheers
Chris Maunder
|
|
|
|
|
Hi Chris
I know you are one of the big bosses
(I like the fact a big boss spends his time talking with users)
I wish to write an article about functional programming. It will be a controversial article (I love functional programming but I think there are excesses)
Years ago, I did such a thing about using "GoTo": a religious war started right away and I lost a lot of points.
Is there, here on CodeProject, a way to constructively criticize a common opinion without being burned in the public square?
Thanks for your time
Vincenzo S.
|
|
|
|
|
Vincenzo,
I would love to see an article like this. I spend a lot of my time questioning the team on why we do certain things and when the answer is "we've always done it this way" I start scratching a little to find the real reason. Good habits are good but it's important to question assumptions.
We could do a couple of things
- Disable voting. I'm not a fan of this but it's an option
- Disable the forum attached to the article, or a softer version is make it so only high rep members can post. Not great, but not terrible
- We help you edit the article, ensuring the introduction makes it clear that the topic is an opinion piece, it's exploratory, and it's intended to generate sensible, constructive debate. We could even ask a couple of the high rep members to keep tabs on it to ensure the tone stays civil.
My preference is #3.
With languages changing so quickly, and our need to switch to potentially unconformable languages becoming more of a thing, it's important we accept different philosophies and styles because sometimes we don't get to code in the manner we'd like to. Sometimes we have to compromise or bend over backwards a little.
cheers
Chris Maunder
|
|
|
|
|
Hi Chris
What do you think about a mix between #3 + #1?
Number 3 should be the right way to go, but I'm sorry to say that not all people know what respect is.
The article will cover functional programming in javascript.
During a "stage de professionalization" for a company in Luxembourg, I discovered that the main application was written forcing javascript to behave as if it were a functional programming language like HASKELL.
Javascript is a multi-paradigm language. In my opinion, forcing it to behave like something it is not, is an aberration.
Who wrote that code is a highly skilled developer that wrote very interesting stuff. I think it would be interesting to involve him in the discussion. (as long as he wants to participate)
Cheers
Vincenzo Stramaglia
|
|
|
|
|
I'm sure we can work out a way to disable voting if that's what's needed.
cheers
Chris Maunder
|
|
|
|
|
Hi Chris
The matter is not about enabling/disabling votes.
A vote is always important because there is always a reason behind any vote. What matters is to understand what the reason is.
There is something in my article that triggers 'downvotes', but how votes are managed by CodeProject doesn't allow me to understand such reasons, and, even worse, downvotes cost me 'reputation points'.
I think, how the 'voting system' is configurated, pushes writers, to write only 'demagogical' articles, and let me say this, in my opinion, is highly detrimental for everybody, CodeProject included.
Since you are one of the big bosses, let me take please the opportunity to express my opinion also about how 'reputation points' are managed. People write free articles in exchange for 'reputation points'. 'Reputation points are like a currency and thus CodeProject' in somehow is like a Bank (when it manages 'reputation points')
I had many 'issues' with my 'reputation points' and that (at the end) was the other reason I left 'CodeProject'.
Regards
Vincenzo Stramaglia
|
|
|
|
|
If you write articles purely to get reputation points then this isn't the site for you.
We, collectively, write articles to share what we know, freely. To help each other. To say thanks to all the other developers who in turn have shared their code and knowledge.
We used to force comments on downvoting specifically to address the issue you raised. Read about why we ditched that.
cheers
Chris Maunder
|
|
|
|
|
We struggle to understand each other, but you are right about one thing: "this is not the site for" me.
Sorry Chris I'm tired of spending time trying to reason with you and your people: at this point, it's pretty clear that we don't share a common way of thinking.
It's time for me to leave. Good luck
Vincenzo
|
|
|
|
|
We have had a report about the solution 52 to this ****Changed to prevent abuse*****[^] Question, where from the 52 solutions I suppose most of the solutions were reported and nuked for spam or site driving.
The questions is still showing the pages account (1 of 3 pages) although there are only 2 remaining answers (1 and 11) and if one click on page 2, then the list is empty.
I suppose that the counters keep track on solutions posted, but not reduce the amount when the solutions are nuked by reports (don't know about other reasons as deleted by protector / staff / owner)
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.
|
|
|
|
|
I'll take a look.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
I accidentally logged in using my Google account, and by doing so I created a new account in addition to the old account I have used for years. How do I remove the new account linked to my Google account? I have looked for a way to remove the account on your web pages, but found nothing.
modified 23-Jun-21 21:01pm.
|
|
|
|
|
Click on your username at the top right to go to your profile page and select "Privacy" (the last tab). This allows the ultimate in privacy: closing your account!
Just make sure you close the correct account.
To associate your Google login with your older account, go to the same page, choose the Account tab, scroll down and select the social login provider(s) you wish to use.
cheers
Chris Maunder
|
|
|
|
|
I am up to publish an article with a lot of Lua code including comments.
The comment lines of the code gets deformed in the publish preview.
Original text:
-- Some comment
function foo( arg)
end
Preview of content to publish:
-- Some comment
function foo( arg)
end
I tried workarounds
1) to use 3 dashes ---
2) spaces in front
3) a dot in front
4) block comments --[[ --]]
Nothing worked
|
|
|
|
|
It's not clear what your problem is (both examples are the same), but the following appears to be correctly formatted:
function foo( arg)
end
|
|
|
|
|
Message Removed
modified 25-May-21 10:50am.
|
|
|
|
|
replace 'trophy' with 'coffee cup'
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
They are one and the same, some days.
cheers
Chris Maunder
|
|
|
|
|
Yesterday I published an article and this morning I discovered I lost lots of reputation points for downvotes.
The article is about an application that runs a model for the spread of covid19.
I Developed the application during the first lockdown. I spent more than 3 months, coding for not less than 10 hours a day.
Receiving a downvote is always frustrating
Receiving a downvote after such an effort without any explanation is mortifying simply because I can do nothing to correct the article
It is too rude and I believe CodeProject shouldn't allow this to happen!
|
|
|
|
|
1x 1-vote
1x 2-Vote
Don't you think that you are overreacting a bit?
I personally think you could explain some more, show a bit of the code, etc. And the end looks like you were not finished when you hit publish... Last sentence is: "One last thought" (without even a point).
So I can imagine that someone gave you the downvote legitimatelly. But yeah, it would be nice to have a reason for the downvote, I agree with you.
An advice from long time member... don't take it too personal.
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.
|
|
|
|
|
Hi Nelek
Maybe I'm overreacting, but be in my shoes, plese.
I spent three months developing that application. Not the downvote is hurting me. Is the lack of any reason. How can I correct properly the article without any clue on what is wrong!
Anyway Thanks for your kindly reply
|
|
|
|
|
I agree that downvoting without comment is rude. Apparently the site used to insist on a comment when downvoting, but how is that going to be policed? To satisfy the requirement, a comment can just say "Sucks!", which is still useless. So the requirement was dropped.
If your article gets a reasonable number of upvotes, the system will automatically purge outlier downvotes. This has happened with a couple of my articles that occasionally trigger people.
|
|
|
|
|
Hi Greg
I think downvoting is an issue that must be fixed. I agree with you that is not easy but I believe the quality of this service will be affected.
For example: talking of my experience: years ago I published an article on a controversial matter (the use of 'goto') I got so many downvotes that I was forced to delete the article.
(maybe the article was not perfect, but what I observed was a kind of religious war against the article and that shouldn't happen!)
anyway...
Thanks for your kindly reply.
|
|
|
|