A "here's a neat tool I made and you can use it too" article
-
If I make a neat tool that I think adds a lot of value for Visual Studio programmers, and that I do not want to charge people money for it --- rather, in order to make the world a better place, I just want to fling it out there, along with its source code and corresponding GitHub repo, would it be acceptable to write a The Code Project article about it, describing why I wrote it, its feature set, how to use it, and such?
-
If I make a neat tool that I think adds a lot of value for Visual Studio programmers, and that I do not want to charge people money for it --- rather, in order to make the world a better place, I just want to fling it out there, along with its source code and corresponding GitHub repo, would it be acceptable to write a The Code Project article about it, describing why I wrote it, its feature set, how to use it, and such?
-
If I make a neat tool that I think adds a lot of value for Visual Studio programmers, and that I do not want to charge people money for it --- rather, in order to make the world a better place, I just want to fling it out there, along with its source code and corresponding GitHub repo, would it be acceptable to write a The Code Project article about it, describing why I wrote it, its feature set, how to use it, and such?
CodeProject is more about knowledge-sharing rather than it is tool sharing. I actively remove articles deemed as tool-sharing from the site. The proper way to post this would be to write an article about your tool. Share the code, how it works, why you made it, what you learned along the way, interesting bits of the full source code, explaining concepts around the code and why you made those decisions. Basically turning your tool into a class lecture and explaining it in a way that the whole class can understand.
Thanks, Sean Ewington CodeProject
-
CodeProject is more about knowledge-sharing rather than it is tool sharing. I actively remove articles deemed as tool-sharing from the site. The proper way to post this would be to write an article about your tool. Share the code, how it works, why you made it, what you learned along the way, interesting bits of the full source code, explaining concepts around the code and why you made those decisions. Basically turning your tool into a class lecture and explaining it in a way that the whole class can understand.
Thanks, Sean Ewington CodeProject
Yes, Sean,
Quote:
Share the code, how it works, why you made it, what you learned along the way, interesting bits of the full source code, explaining concepts around the code and why you made those decisions. Basically turning your tool into a class lecture and explaining it in a way that the whole class can understand.
Maybe I was not communicating well enough, but that was exactly what I was intending to do. The only issue is, each tool has over 100 Visual Studio projects as part of its solution and is written in a production-level fashion. I assume a multi-part article series would also be acceptable, so I did not have one really huge article covering the gamut of the effort. Would that also be acceptable? Regards, Brian Hart
-
Yes, Sean,
Quote:
Share the code, how it works, why you made it, what you learned along the way, interesting bits of the full source code, explaining concepts around the code and why you made those decisions. Basically turning your tool into a class lecture and explaining it in a way that the whole class can understand.
Maybe I was not communicating well enough, but that was exactly what I was intending to do. The only issue is, each tool has over 100 Visual Studio projects as part of its solution and is written in a production-level fashion. I assume a multi-part article series would also be acceptable, so I did not have one really huge article covering the gamut of the effort. Would that also be acceptable? Regards, Brian Hart
I guess it depends on how many multi-part we're talking. Five parts is OK. I'd say that's a good and reasonable maximum. Otherwise huge article is totally appropriate. Members even seem to like it.
Thanks, Sean Ewington CodeProject
