Thoughts on posting articles
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
Susan Hernandez wrote: What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers? When I read the articles here, I'm personally as much interested in the writing style as I am in the technology being introduced. If you cover well travelled ground in an entertaining way, I think that's valuable too. Please use the right HTML formatting though. The wizard makes it pretty easy, but some people seem to go far out of their way to make their article look inconsistent with the rest of the site. Susan Hernandez wrote: Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter? I am "lucky" to have an hour and a bit of train commuting time each day, and a laptop to help pass the time. Once I have an idea I think will make a good article, I mull it over for a couple of weeks trying to refine it, then start actually writing it. I write on the weekend when it's getting close to being done, and I just have a couple of hours left. Writing articles here is fun, and great personal development. The first one is a big self-confidence hurdle, especially if you post using your real name and not a pseudonym, but I think you'll find the experience generally pretty rewarding. Just my 2 cents. Sean
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
Susan Hernandez wrote: articles already exist on the subject Great questions. I have been floundering myself, but anyway.... Personally, I like to read several different articles on the same subject or nearly the same. People have different thought processes and you might have a way to do something that I never thought of doing before. Or, you might be able to explain COM in English.... :-) I can't tell you how many times that I have been reading articles on here that I thought, "What a great idea! Never thought of doing it that way before". By all means post away!
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
Don't pretend to be more than you are. 1. Be honest. At the beginning explain it's your first one and that it might be similar to other articles. Let people know up front what they are going to conclude on their own anyway. 2. If it's a C++ article or a C# article try and find someone here that's established themselves as knowing their stuff. Email it to them and just have them browse it. I wouldn't ask them to fix it but maybe just make some small suggestions over-all. It should be your work not theirs and you won't learn by being propped up. (The US has tried this with foreign governments and it never works. Propping up is just bad.) 3. When you post it have your first paragraph be very short but explain, "This is my first article and I'm not an expert but I want to contribute. Feedback is very welcome but try and make it constructive. I'm new to this and wish to learn in a constructive way. I will try to follow-up on all well intended comments." - I don't think disclaimers ever hurt and it's good to let your audience know you don't want to play hard-ball with them. 4. If you do steps 1 - 3 don't be surprised if it attracts the attention of some of the better authors here. You will probably get some excellent feedback and learn way more from the experience than you hoped to share with others. 5. You have to trust this community. It's a very fair place (or so it seems). This is life you have to take some chances. Birds only learn how to fly by jumping out of the nest. Give it a try and see how it goes. I'm sure it will be a pleasant and rewarding experience. I'm working on two articles myself. One to answer the question "What makes a good programmer" and the other, "Designing packaging and deploying a simple application in Visual C++". I'm in no great hurry on either. I'm self employed and so I budget my time appropriately. Some weeks I'll give it 30 minutes to an hour and others may not get attention at all. When I'm satisfied and have taken a few days to read over it and have not changed anything I've identified 2 people here that I will have read both articles. One very technical and the other an extremely good communicator and technical. I think a very good exercise for you would be to plan it out. Identify your subject (don't worry if it's a repeat, there's no way it really could be because it's coming from your perspective), pick a schedule for it. You might only allocate 1 hour a week and that's fine. Then carefully plan things. Make it a full exercise that you will benefit from as
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
I appreciate the time everyone has taken replying to my question. I was a little hesitant, because I've seen just so many excellent programmers here. I definitely have always enjoyed constructive criticism, and don't take it poorly, as that's the best way to learn. In my former life I was a lead in a lot of community theater musicals, and criticism is all you get. I am now wondering if my first article should tackle a subject I feel very comfortable with, or if it should express something new I just learned. I'm tending to the "just learned". For example, I'm trying to research writing a tool or helper to go through an entire Visual Source Safe tree and, through the command line, fake a "recursive" rollback to a label. When I figure it out to my personal satisfaction, I'm thinking of sharing that with the community. Anyway, thanks again for all of the great comments and encouragement. Susan
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
I think all of the previous posters pretty well answered your questions. I would just like to add one more reason to post: improving your code. You mention "giving back to CodeProject", and that's a great reason by itself; but don't forget that everytime you submit an article, it will be read - and the code inspected - by hundreds of people. In effect, you will get hundreds of free code reviews, plus maybe some good suggestions for improving it. So each time you give to CP, you get something (very valuable) in return. If companies realized the benefit of code review & testing, they would insist that their programmers post critical pieces of code on CP. Don't be shy about submitting an article and then updating it the next day when someone points out an obvious problem - I have done that many times. If you use the Article Submission Wizard, it takes only a few minutes to re-submit. Best wishes, Hans
-
Susan Hernandez wrote: articles already exist on the subject Great questions. I have been floundering myself, but anyway.... Personally, I like to read several different articles on the same subject or nearly the same. People have different thought processes and you might have a way to do something that I never thought of doing before. Or, you might be able to explain COM in English.... :-) I can't tell you how many times that I have been reading articles on here that I thought, "What a great idea! Never thought of doing it that way before". By all means post away!
I have been told by co-workers that I'm pretty decent with explaining things "in English" to non-techies. That's why I was thinking targetting to beginners. Thanks for the comment.
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
I'll give you a five provided you send me a few dozen packets of Jelly Belly's That shouldn't be so difficult for you to do should it ? ;)
-
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
Susan Hernandez wrote: What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers? There's a lot of value in a beginner article, because it addresses an issue 1) from a position in which we've all been at or are currently at, 2) because it doesn't complicate things. That said, a beginner article probably should focus more on why the solution works for you, and think about where the solution might not work for others, or further investigation that would be worthwhile. Susan Hernandez wrote: What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced? If your idea/implementation contributes something new or unique, or you feel you can say it better, or you feel that a beginner article is really needed (this is very often the case!), then go for it. Susan Hernandez wrote: Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter? You're going to think I'm crazy, but writing articles is something I do to "escape" from my normal consulting work. Or, it's something cool that I get permission from my client to write about. I tend to have a lot of creative endeavors going on, and frankly, the must be fed (or nurtured, if you prefer). So, I make the time. I sometimes stay up late. If I'm stuck on a problem, I work on something else (like the code for an article). Being a consultant, I work on client stuff anytime and anywhere, as required, so I fit my personal time in where I can as well. And sometimes, I simply say "the heck with it, I need to work on MY stuff for a while." Ultimately, you decide to make the time. Get up an hour earlier, don't watch that TV show, etc. I will say, it is VERY rewarding. Susan Hernandez wrote: Given these questions, my query is - To Post or Not to Post? Of course you should post. I was pretty nervous about my first article (Organic Programming, hehehe). If you want a proof-reader, send it my way and I'll look it over. Marc My website
Latest Articles: Object Comparer -
Susan Hernandez wrote: What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers? There's a lot of value in a beginner article, because it addresses an issue 1) from a position in which we've all been at or are currently at, 2) because it doesn't complicate things. That said, a beginner article probably should focus more on why the solution works for you, and think about where the solution might not work for others, or further investigation that would be worthwhile. Susan Hernandez wrote: What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced? If your idea/implementation contributes something new or unique, or you feel you can say it better, or you feel that a beginner article is really needed (this is very often the case!), then go for it. Susan Hernandez wrote: Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter? You're going to think I'm crazy, but writing articles is something I do to "escape" from my normal consulting work. Or, it's something cool that I get permission from my client to write about. I tend to have a lot of creative endeavors going on, and frankly, the must be fed (or nurtured, if you prefer). So, I make the time. I sometimes stay up late. If I'm stuck on a problem, I work on something else (like the code for an article). Being a consultant, I work on client stuff anytime and anywhere, as required, so I fit my personal time in where I can as well. And sometimes, I simply say "the heck with it, I need to work on MY stuff for a while." Ultimately, you decide to make the time. Get up an hour earlier, don't watch that TV show, etc. I will say, it is VERY rewarding. Susan Hernandez wrote: Given these questions, my query is - To Post or Not to Post? Of course you should post. I was pretty nervous about my first article (Organic Programming, hehehe). If you want a proof-reader, send it my way and I'll look it over. Marc My website
Latest Articles: Object ComparerMarc Clifton wrote: If you want a proof-reader, send it my way and I'll look it over. Wow, my gosh thanks. I have read many of your articles. Many of them are way over my head :-D And as Garth from the previous post suggested, many Jelly Belly's to those who help proof-read... :laugh:
-
I appreciate the time everyone has taken replying to my question. I was a little hesitant, because I've seen just so many excellent programmers here. I definitely have always enjoyed constructive criticism, and don't take it poorly, as that's the best way to learn. In my former life I was a lead in a lot of community theater musicals, and criticism is all you get. I am now wondering if my first article should tackle a subject I feel very comfortable with, or if it should express something new I just learned. I'm tending to the "just learned". For example, I'm trying to research writing a tool or helper to go through an entire Visual Source Safe tree and, through the command line, fake a "recursive" rollback to a label. When I figure it out to my personal satisfaction, I'm thinking of sharing that with the community. Anyway, thanks again for all of the great comments and encouragement. Susan
Susan Hernandez wrote: For example, I'm trying to research writing a tool or helper to go through an entire Visual Source Safe tree and, through the command line, fake a "recursive" rollback to a label. When I figure it out to my personal satisfaction, I'm thinking of sharing that with the community. Sounds great, and also sounds quite unique. If I might ask, why have you needed this feature? The reason I'm asking is that my client is evaluating different version control systems, and I'm only familiar with CVS, so I'd like to know more about useful features. Thanks! Marc My website
Latest Articles: Object Comparer String Helpers -
Marc Clifton wrote: If you want a proof-reader, send it my way and I'll look it over. Wow, my gosh thanks. I have read many of your articles. Many of them are way over my head :-D And as Garth from the previous post suggested, many Jelly Belly's to those who help proof-read... :laugh:
Susan Hernandez wrote: many Jelly Belly's Well, hopefully the gym and biking 10 miles a day will help to work off mine! :-D Marc My website
Latest Articles: Object Comparer String Helpers -
Susan Hernandez wrote: For example, I'm trying to research writing a tool or helper to go through an entire Visual Source Safe tree and, through the command line, fake a "recursive" rollback to a label. When I figure it out to my personal satisfaction, I'm thinking of sharing that with the community. Sounds great, and also sounds quite unique. If I might ask, why have you needed this feature? The reason I'm asking is that my client is evaluating different version control systems, and I'm only familiar with CVS, so I'd like to know more about useful features. Thanks! Marc My website
Latest Articles: Object Comparer String HelpersMarc Clifton wrote: ...evaluating different version control systems Honestly, I have not tried other versioning control systems. However, I have heard so many people saying that VSS is sub-par at best, and that's being nice. In my case, I am not sure why we use VSS per se, other than it comes with and integrates somewhat nicely with Visual Studio. We don't have a whole lot of time to research other systems; however that being said, we're really going to take a look at Team System, which is "supposed" to be "really great". Of course, this makes sense for us as all our new development is pretty much on .NET. Marc Clifton wrote: If I might ask, why have you needed this feature? I am trying to integrate Microsoft's Enterprise Library into our existing code. If you are not familiar, it's free source code they provide, based entirely on the .NET framework. The source code provides common, yet extensible helpers for Caching, Configuration, Database access, Exception handling, Logging, and Security. They have about 5-6 levels of projects at any given point, when you add this project to source control. They have a new release out, which is very different from the original, however I'm trying to integrate it in with the original branch, which has some changes I've done. Of course I messed up the first time, but I thought ahead and had put a label on it. I simply wanted to roll back to the label, but Lo and Behold, Source Safe explorer does not allow you a recursive rollback. You have to do it file......by file.....by file.... The best I found was using a command line tool, and in that way, you can at least do all files in a project...
SS.exe Rollback "$/MyRootProject/*" "-VLProj Label w Spaces" SS.exe Rollback "$/MyRootProject/SubProject1/*" "-VLProj Label w Spaces" SS.exe Rollback "$/MyRootProject/SubProject2/*" "-VLProj Label w Spaces"Interestingly enough...although I have found document after document that says I'm supposed to be able to do this, it's not working for me ... yet. That's what started this whole discussion... I first "asked" if anyone knew how (http://www.codeproject.com/script/comments/forums.asp?msg=1198193&forumid=1641#xx1198193xx)[ -
Marc Clifton wrote: ...evaluating different version control systems Honestly, I have not tried other versioning control systems. However, I have heard so many people saying that VSS is sub-par at best, and that's being nice. In my case, I am not sure why we use VSS per se, other than it comes with and integrates somewhat nicely with Visual Studio. We don't have a whole lot of time to research other systems; however that being said, we're really going to take a look at Team System, which is "supposed" to be "really great". Of course, this makes sense for us as all our new development is pretty much on .NET. Marc Clifton wrote: If I might ask, why have you needed this feature? I am trying to integrate Microsoft's Enterprise Library into our existing code. If you are not familiar, it's free source code they provide, based entirely on the .NET framework. The source code provides common, yet extensible helpers for Caching, Configuration, Database access, Exception handling, Logging, and Security. They have about 5-6 levels of projects at any given point, when you add this project to source control. They have a new release out, which is very different from the original, however I'm trying to integrate it in with the original branch, which has some changes I've done. Of course I messed up the first time, but I thought ahead and had put a label on it. I simply wanted to roll back to the label, but Lo and Behold, Source Safe explorer does not allow you a recursive rollback. You have to do it file......by file.....by file.... The best I found was using a command line tool, and in that way, you can at least do all files in a project...
SS.exe Rollback "$/MyRootProject/*" "-VLProj Label w Spaces" SS.exe Rollback "$/MyRootProject/SubProject1/*" "-VLProj Label w Spaces" SS.exe Rollback "$/MyRootProject/SubProject2/*" "-VLProj Label w Spaces"Interestingly enough...although I have found document after document that says I'm supposed to be able to do this, it's not working for me ... yet. That's what started this whole discussion... I first "asked" if anyone knew how (http://www.codeproject.com/script/comments/forums.asp?msg=1198193&forumid=1641#xx1198193xx)[Susan Hernandez wrote: but Lo and Behold, Source Safe explorer does not allow you a recursive rollback. You have to do it file......by file.....by file.... :omg: Wow, that's awful. Geez, the code base we're using CVS with has hundreds of files, and that's probably a small project by some comparisons! I'd hate to have to manually rollback each file. Susan Hernandez wrote: it's not working for me ... yet. Good luck! Having fought "documentation" before, I can relate to how frustrating it can be. Susan Hernandez wrote: I'll write the article on it. Sounds like a very useful utility. Poking around, there's some interesting flags that this fellow mentions in his blog.[^] This[^] was interesting too. Well, anyways... Marc My website
Latest Articles: Object Comparer String Helpers -
I am looking for opinions on posting articles on CodeProject.
- What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers?
- What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced?
- Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter?
Given these questions, my query is - To Post or Not to Post? I have seen a great article on how to structure your article submission (thanks Marc Clifton) but figuring out when to post is the issue. I want to give back to CodeProject, but I'm not sure how. Thanks for any feedback. Susan J Hernandez
Susan Hernandez wrote: What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers? I would strongly recommend against doing this. If you contribute an article on a topic you aren't very sure about, you risk contaminating other newbies with incorrect information. Susan Hernandez wrote: What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced? If you have worked on a topic and the only articles available are on advanced areas related to that topic, it would be a good idea to write a beginner level article on that topic. Susan Hernandez wrote: Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter? I write my articles mostly during friday nights and the weekends. Some of the content-knowledge of my article - I may have gained while at work or while doing some R/D work at home.
-
Susan Hernandez wrote: What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers? I would strongly recommend against doing this. If you contribute an article on a topic you aren't very sure about, you risk contaminating other newbies with incorrect information. Susan Hernandez wrote: What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced? If you have worked on a topic and the only articles available are on advanced areas related to that topic, it would be a good idea to write a beginner level article on that topic. Susan Hernandez wrote: Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter? I write my articles mostly during friday nights and the weekends. Some of the content-knowledge of my article - I may have gained while at work or while doing some R/D work at home.
Nishant Sivakumar wrote: I would strongly recommend against doing this. If you contribute an article on a topic you aren't very sure about, you risk contaminating other newbies with incorrect information. I thank you for your honest and up-front answers. Interestingly enough, most people that have answered this post have a different opinion - they seem to suggest that as long as I mention that I'm a newbie and am open to corrections, that it's ok. I do see your point, I don't want to post incorrect information. That right there was exactly what I was getting at in my original post. I'm wondering, though, how many article posters have posted articles that have been somewhat wrong, and then they were corrected by commenters, and then they corrected their articles. In any case, I have been offered by some very nice CP members that if I do post an article, they offer to screen it for blatant errors before I post it. Perhaps that is a good compromise - making sure it at least meets a minimum standard before I post? Thanks again for your comments. Sue
-
Susan Hernandez wrote: but Lo and Behold, Source Safe explorer does not allow you a recursive rollback. You have to do it file......by file.....by file.... :omg: Wow, that's awful. Geez, the code base we're using CVS with has hundreds of files, and that's probably a small project by some comparisons! I'd hate to have to manually rollback each file. Susan Hernandez wrote: it's not working for me ... yet. Good luck! Having fought "documentation" before, I can relate to how frustrating it can be. Susan Hernandez wrote: I'll write the article on it. Sounds like a very useful utility. Poking around, there's some interesting flags that this fellow mentions in his blog.[^] This[^] was interesting too. Well, anyways... Marc My website
Latest Articles: Object Comparer String HelpersIt's funny, about 15 minutes before your reply, I "found" (finally) on Google some mention of a Source Safe COM API that I can use from my .NET application. I found it (C:\Program Files\Microsoft Visual Studio\VSS\win32\SSAPI.dll), and started floundering with it, and then I got your post - one of your links shows a guy using this API! Break for me! :) Thanks for posting the links. I did look on Google, and I even found the first link that you posted, but the exact syntax mentioned in the article doesn't work for me, and I can't figure out why. But I may not have to use the Command line, if I can get the API going. Still, I think I will figure out the command line problem anyway, as a matter of interest. And one last comment: I mentioned to my boss last evening what I was researching and why, and he actually said "when you figure it out, write an article for Code Project" ! He actually gave me the go-ahead to spend work time to do it, too, because he really does understand the importance of practicing technical writing, and the benefits of research. WOW! I'm lucky. Thanks for all your help and great comments. I'll stop posting now, and start actually researching for the article. :-D
-
It's funny, about 15 minutes before your reply, I "found" (finally) on Google some mention of a Source Safe COM API that I can use from my .NET application. I found it (C:\Program Files\Microsoft Visual Studio\VSS\win32\SSAPI.dll), and started floundering with it, and then I got your post - one of your links shows a guy using this API! Break for me! :) Thanks for posting the links. I did look on Google, and I even found the first link that you posted, but the exact syntax mentioned in the article doesn't work for me, and I can't figure out why. But I may not have to use the Command line, if I can get the API going. Still, I think I will figure out the command line problem anyway, as a matter of interest. And one last comment: I mentioned to my boss last evening what I was researching and why, and he actually said "when you figure it out, write an article for Code Project" ! He actually gave me the go-ahead to spend work time to do it, too, because he really does understand the importance of practicing technical writing, and the benefits of research. WOW! I'm lucky. Thanks for all your help and great comments. I'll stop posting now, and start actually researching for the article. :-D
Susan Hernandez wrote: and he actually said "when you figure it out, write an article for Code Project" ! He actually gave me the go-ahead to spend work time to do it :jig: :-D Marc My website
Latest Articles: Object Comparer String Helpers -
I'll give you a five provided you send me a few dozen packets of Jelly Belly's That shouldn't be so difficult for you to do should it ? ;)
Garth Watkins wrote: I'll give you a five provided you send me a few dozen packets of Jelly Belly's That shouldn't be so difficult for you to do should it ? Garth: I had asked a while ago on CodeProject's lounge about writing articles. You commented "Write it, I'll rate it" ... are you still willing? I have finally finished a first draft, and I have posted the information on my blog[^] with a link to where the sample article resides and a section for posting comments. If you'd give it a once-over when you get time, I'd really appreciate it. All I'm looking for is blatant errors - things I'm saying that are completely wrong or off base. I know I won't be perfect, and that's OK - I just don't want to give misinformation. And I'd be happy to send you some jellybelly's..... :-)
-
Susan Hernandez wrote: What if one is a beginner ones-self, and is concerned about writing an article that may not have the "perfect" answers? There's a lot of value in a beginner article, because it addresses an issue 1) from a position in which we've all been at or are currently at, 2) because it doesn't complicate things. That said, a beginner article probably should focus more on why the solution works for you, and think about where the solution might not work for others, or further investigation that would be worthwhile. Susan Hernandez wrote: What if one (or several) articles already exist on the subject one is interested in? What if those existing articles are more advanced? If your idea/implementation contributes something new or unique, or you feel you can say it better, or you feel that a beginner article is really needed (this is very often the case!), then go for it. Susan Hernandez wrote: Where in the world does one get the time to write articles - do most of the posters post (a) while in work; (b) late at night after work; (c) on weekends; or (d) you own your own business so it does not matter? You're going to think I'm crazy, but writing articles is something I do to "escape" from my normal consulting work. Or, it's something cool that I get permission from my client to write about. I tend to have a lot of creative endeavors going on, and frankly, the must be fed (or nurtured, if you prefer). So, I make the time. I sometimes stay up late. If I'm stuck on a problem, I work on something else (like the code for an article). Being a consultant, I work on client stuff anytime and anywhere, as required, so I fit my personal time in where I can as well. And sometimes, I simply say "the heck with it, I need to work on MY stuff for a while." Ultimately, you decide to make the time. Get up an hour earlier, don't watch that TV show, etc. I will say, it is VERY rewarding. Susan Hernandez wrote: Given these questions, my query is - To Post or Not to Post? Of course you should post. I was pretty nervous about my first article (Organic Programming, hehehe). If you want a proof-reader, send it my way and I'll look it over. Marc My website
Latest Articles: Object ComparerMarc Clifton wrote: Of course you should post. I was pretty nervous about my first article (Organic Programming, hehehe). If you want a proof-reader, send it my way and I'll look it over. Marc: I had asked a while ago on CodeProject's lounge about writing articles. You commented that you might be willing to proof-read it ... are you still willing? I have finally finished a first draft, and I have posted the information on my blog[^] with a link to where the sample article resides and a section for posting comments. If you'd give it a once-over when you get time, I'd really appreciate it. All I'm looking for is blatant errors - things I'm saying that are completely wrong or off base. I know I won't be perfect, and that's OK - I just don't want to give misinformation. And I'd be happy to send you some jellybelly's..... :-)