hmmmmm.... should I write my first article
-
No, you were looking for ways to limit to only one active copy of the software at anytime... we were suggesting hardware locks and some vendors of software keys. You had also mentioned that you had some pseudo worked out, which I am (still) very much interested in :)
Oh yes, that was indeed for copyright restrictions. There is only one bug left in the lgic, once i have covered that i will start getting it ready for coding.
Brad Australian - Christian Graus on "Best books for VBscript" A big thick one, so you can whack yourself on the head with it.
-
The subject came up again today at work over parallel programming. Others here have encouraged me to write an article, and although I have argued against it because of the difficult with work. I am tired of having to explain the concepts over and over again one person at a time. The question is, do I do it as an internal white paper only (all the writing, none of the review) only for people at work, or do I write for public access as well? So are there already too many articles on threading? I have rarely seen people talk about atomic operations, massively parallel, cooperatively asynchronous operation, and lock-free programming. But the better question is, does anyone really care? I can easily do it internal only for my team, and maybe other teams at other similar facilities, but if the subject is really desirable, maybe it needs to be wider?
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Richie308 wrote:
what would be the harm in letting us read it also?
It has to pass through the company approval process, as well as other approval processes before it ever gets to CP, even if I write it at home. Writing it for work only, means none of the approval is necessary, just optional. Writing it for CP means I can release it internally and then go through the slower approval and editing for external release. It's more effort basically. But if it is something that is desired, I could probably break it into a series, it's a complex issue. Atomic Parallelization: all of the power of parallel, none of the WMD.... ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
If you write it at home in your spare time you are not allowed to post it on CP?!? :confused:
-
The subject came up again today at work over parallel programming. Others here have encouraged me to write an article, and although I have argued against it because of the difficult with work. I am tired of having to explain the concepts over and over again one person at a time. The question is, do I do it as an internal white paper only (all the writing, none of the review) only for people at work, or do I write for public access as well? So are there already too many articles on threading? I have rarely seen people talk about atomic operations, massively parallel, cooperatively asynchronous operation, and lock-free programming. But the better question is, does anyone really care? I can easily do it internal only for my team, and maybe other teams at other similar facilities, but if the subject is really desirable, maybe it needs to be wider?
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Jeffry J. Brickley wrote:
So are there already too many articles on threading?
Threading is different than parallel programming.
Jeffry J. Brickley wrote:
But the better question is, does anyone really care?
I would, and I think it's where programming needs to head.
Jeffry J. Brickley wrote:
but if the subject is really desirable, maybe it needs to be wider?
I'd love to see an article on the subject! Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
If you write it at home in your spare time you are not allowed to post it on CP?!? :confused:
Robert Rohde wrote:
If you write it at home in your spare time you are not allowed to post it on CP?!?
:-D exactly. Otherwise I could be giving out company sensitive information on the side. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
The subject came up again today at work over parallel programming. Others here have encouraged me to write an article, and although I have argued against it because of the difficult with work. I am tired of having to explain the concepts over and over again one person at a time. The question is, do I do it as an internal white paper only (all the writing, none of the review) only for people at work, or do I write for public access as well? So are there already too many articles on threading? I have rarely seen people talk about atomic operations, massively parallel, cooperatively asynchronous operation, and lock-free programming. But the better question is, does anyone really care? I can easily do it internal only for my team, and maybe other teams at other similar facilities, but if the subject is really desirable, maybe it needs to be wider?
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Certain authors are enjoyable to read even if the subject matter isn't immediately applicable. I'd read it :D
Todd Smith
-
Robert Rohde wrote:
If you write it at home in your spare time you are not allowed to post it on CP?!?
:-D exactly. Otherwise I could be giving out company sensitive information on the side. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
But if it has nothing to do with your company? Following this rule one could also state that you could reveal company sensitive information by posting here or in any other forum. Think about it: By posting the restrictions made by your company you are already giving out information... Robert
-
But if it has nothing to do with your company? Following this rule one could also state that you could reveal company sensitive information by posting here or in any other forum. Think about it: By posting the restrictions made by your company you are already giving out information... Robert
-
The defense industry errs on the side of paranoia on these sorts of things. If you find the restrictions unacceptable you're free to seek employment elsewhere in the private sector.
-- Rules of thumb should not be taken for the whole hand.
It wasn't meant as an offense. I'm just curious where this restriction ends. Is he allowed to post recipes on
CookProject.com? Or is he allowed to answer threading related questions in the programming forums? :confused: -
Certain authors are enjoyable to read even if the subject matter isn't immediately applicable. I'd read it :D
Todd Smith
Todd Smith wrote:
ForumThe Lounge Subject:Re: hmmmmm.... should I write my first article Sender:Todd Smith Date:13:12 6 Feb '07 Certain authors are enjoyable to read
You obviously have never read one of my papers! :laugh:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
It wasn't meant as an offense. I'm just curious where this restriction ends. Is he allowed to post recipes on
CookProject.com? Or is he allowed to answer threading related questions in the programming forums? :confused:Robert Rohde wrote:
Is he allowed to post recipes
not really, under new regs that could remove profit from a Denny's that has a recipe for Pancakes... my grandfather made the best pancakes in the world, but if I tell that recipe someone could be making a profit -- but even if they are not, if there is the potential for a knowledge that I have (my grandfather's pancake recipe), that "could" make a profit, then it should not be released. It all depends on who is on the approval process at the time. I have heard at least one quote say that if the approval team had their way, no one would write anything anywhere to anyone at anytime. But they do recognize that would be impossible to handle, so this is the solution middle-ground.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
The defense industry errs on the side of paranoia on these sorts of things. If you find the restrictions unacceptable you're free to seek employment elsewhere in the private sector.
-- Rules of thumb should not be taken for the whole hand.
who said DI? ;P:rolleyes:;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
who said DI? ;P:rolleyes:;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
A number of your old posts that I don't have the time to dig up. :doh:
-- Rules of thumb should not be taken for the whole hand.
dan neely wrote:
A number of your old posts that I don't have the time to dig up.
I was teasing. :-D I hedge 95% of the time, and admit the other 5% :rolleyes:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)