That is really great info. Unfortunately the site only has data for professional (== expensive) cameras. Any idea if someone has something similar for consumer models?
I'd be really interested even for a general "For this camera it is useful to buy a good memory card." result for my Nikon Coolpics 8700. The damn RAW images save forever...
It actually isn't that bad. I'm from Finland and we have it the same way. Overall it's good to know roughly what other people are making where you work - how else would you if they are giving you half what you deserve?
Some people here think that it promoted envy, but I think that's everyones personal problem. You just have to be able to handle someone making more money if they are worth more then you.
What kind of "potential for privacy abuse" do you actually mean? If you know the persons name and address you get a number, it's not like you can get the whole tax form.
Ok. I learned OOP in my freshman year too. Then, after graduation and a couple years of experience I realized that I didn't know shit on my freshman year. OOP really is something that takes both experience and theory to be really powerful.
In fact, I'd say the first two years after graduation I was a pretty crappy developer. I didn't know it of course, but later it has really hit me.
Well, I'm not a professional photographer but I own a Nikon Coolpics 8700 that has NEF support. I have been using a plugin for photoshop provided by Nikon and at least for this camera - that plugin is utter crap.
It is painfully slow, even for transferring just a few images to JPG/Photoshop. It is in fact so slow that I bought a $25 shareware app that is 10 times faster and actually has a batch mode.
So I think Nikon should stick with the Cameras and let Adobe do the NEF support.
My experience (mostly theoretical) is with AspectJ (Java), but I guess that doesn't really matter. The simple explanation I would give is this:
You define Pointcuts which are points in you application execution such as: before the start of a method that matches a regular expression (like set.*).
You define Advice that is a function/method that is executed at a given pointcut.
And then your code is executed e.g. before a setter method is called on some/any objects. This allows you to open transactions as they are needed or handle exceptions outside the business code. Probably allows you to do all kinds of other stuff too, but those are the two obvious things that I've come up with.
You are 100% correct, but the whole world (except me and maybe you) uses outlook and for some reason people using outlook always reply to the sender address.
I'm not sure if outlook ignores reply-to or if it just asks a question with the sender address as default choice, but for some reason I always get the replys to the wrong address.
Slashdot Mirror
That is really great info. Unfortunately the site only has data for professional (== expensive) cameras. Any idea if someone has something similar for consumer models?
I'd be really interested even for a general "For this camera it is useful to buy a good memory card." result for my Nikon Coolpics 8700. The damn RAW images save forever...
It actually isn't that bad. I'm from Finland and we have it the same way. Overall it's good to know roughly what other people are making where you work - how else would you if they are giving you half what you deserve?
Some people here think that it promoted envy, but I think that's everyones personal problem. You just have to be able to handle someone making more money if they are worth more then you.
What kind of "potential for privacy abuse" do you actually mean? If you know the persons name and address you get a number, it's not like you can get the whole tax form.
Ok. I learned OOP in my freshman year too. Then, after graduation and a couple years of experience I realized that I didn't know shit on my freshman year. OOP really is something that takes both experience and theory to be really powerful.
In fact, I'd say the first two years after graduation I was a pretty crappy developer. I didn't know it of course, but later it has really hit me.
Well, I'm not a professional photographer but I own a Nikon Coolpics 8700 that has NEF support. I have been using a plugin for photoshop provided by Nikon and at least for this camera - that plugin is utter crap.
It is painfully slow, even for transferring just a few images to JPG/Photoshop. It is in fact so slow that I bought a $25 shareware app that is 10 times faster and actually has a batch mode.
So I think Nikon should stick with the Cameras and let Adobe do the NEF support.
Well, at least around here the telcos didn't fail. The governament just transformed them in to companies and sold the stock to private investers.
So now, instead of the governament monopoly, we have a private monopoly. Hooray!
My experience (mostly theoretical) is with AspectJ (Java), but I guess that doesn't really matter. The simple explanation I would give is this:
You define Pointcuts which are points in you application execution such as: before the start of a method that matches a regular expression (like set.*).
You define Advice that is a function/method that is executed at a given pointcut.
And then your code is executed e.g. before a setter method is called on some/any objects. This allows you to open transactions as they are needed or handle exceptions outside the business code. Probably allows you to do all kinds of other stuff too, but those are the two obvious things that I've come up with.
You are 100% correct, but the whole world (except me and maybe you) uses outlook and for some reason people using outlook always reply to the sender address.
I'm not sure if outlook ignores reply-to or if it just asks a question with the sender address as default choice, but for some reason I always get the replys to the wrong address.
I just gave them 20 . Nothing eartshattering or "noteworthy", but that's my share. They aren't looking for Bill Gates here - give what you can.