You could do what I did with my camera (if yours lets you, I had a Canon G3 and a G1 before that).
First manually set your focus and aperature to the hyperfocal (get rid of wasted time with autofocus and its pretty much what you want for indoor shooting anyway).
And second, take some test shots with flash and decide what ISO and flash setting was best (I think I could do flash compensation, I never played with that) and set those manually. While you are at it lock the white balance.
Lastly take all the pictures you want without the delay of all the "auto" features and know in advance that the camera is going to do more or less the right thing in the environment you are in.
The canon powershot G series (G1, G2, G3, G5, G6) all have decent burst modes that achieve multiple frames a second and they have an average price of around $500 (depending on which model you want). This requires you to anticipate the shots you want though. What always bothered me about my G1 and G3 was how long it took to shoot an unprepared (and non-focus locked) shot. Over a second for the camera to auto-focus and calculate white balance and exposure. You could get around this by locking focus and manually chosing white balance and exposure. Then it was about 2/3 a second to take the shot. Recovery time wasn't too hot either.
Get a book on film photography and read that. The basics are the same, digital cameras with any complexity mimic the film camera analogs very closely. Of course after you have read the books on film photography the books that tell you how digital cameras differ will make much more sense.
I also recommend browsing around the web starting at a good Digital Camera site. I managed to find some great info on shooting with digital cameras by doing this.
When I was trained to type, I was told that if you needed to capitalize more than 2 characters in a row you should use caps lock. Its far more efficient and does not strain your hands nearly so much.
From the responses I've seen I think the sad truth is a rare few programmers have been formally trained in typing. If you had this article would sound completely ridiculous to you as well.
You hit the major key. Its about planning ahead and being realistic. I just went through a major planning where I work, and we were asked to cut our estimates by over 50% but everyone had planned ahead and we were able to identify features that could be left out in order to shorten the schedule and as such noone has to work extra hours to meet the shortened time.
It may not be possible to get this respect and consideration from the managers where you work in which case you might need to look elsewhere.
On the other side of the coin more hours does not necessary mean more productivity. It may be fully possible to optimise your work time and priorities and manage to get all the work that needs to be done finished during normal hours and no need for extended periods of long hours.
In the state I grew up in it was completely legal for anyone at all to carry a gun so long as it was not concealed. City law could override this, but in general you could carry any weapon so long as everyone knew you were carrying it.
I don't think there were really that many more injuries from guns (hunting excepted of course, a group of 6 or 8 drunk men with high powered rifles makes for a less than safe outing) than other states I've been in and read the news.
I started out programming in BASIC, moved on to pascal with little problems and even understood procedures and functions quite well, later learned OOP and did great with that though it took me a while to get rid of some of my procedural bad habits (useful habits in some cases I must say).
Anyways, BASIC isn't horrible to start with, the key is knowing what parts of your starting language still apply and what parts you should leave behind.
Maybe I'm a special case but I know many other incredible programmers that started programming in BASIC and have beautiful structured and OO code.
I get what you are going at, but along another different but related line, the problem may not be the language used but instead the teaching method being employed.
I've found that most people with even a small interest in programming (yes I've found some to where this won't apply) will understand how if you find the right approach to explaining it. The key is to start small and keep trying new ways to explain stuff until it sticks. The approach that worked well for me way back in the day was the BASIC programming book included with the TRS-80 color computer. If I were to attempt to teach someone to program I'd use that book as a model in the language of my choice.
Important features of a language to teach a beginner are:
Interpreted language, removes complication of compilation. It should preferably be a language where the execution and editor are mixed together. Its nice to type a few lines, and then type run (or click a "run" button) and see the results. One that has a debug stepper right inside the editor would be excellent as stepping through a simple program seems like it would be a great way to help explain what is happening from step to step. I think that maybe Oberon has that sort of feature built in, and I'm sure there are free distributions of it available.
A small set of well defined errors that have decent explainations. They should quickly show you where the error is in the code and give you a very good idea whats wrong. Syntax Error doesn't seem like it fits the bill, but it would direct you to a line number, possibly even a column number, and would tell you that "you made a typo of some sort".
No requirement to "delcare" variables. Later in life its very important to have the type checking that this provides but for beginners it makes no sense. They want to say that "myVariable" gets the value 10 + "myOtherVariable" and just have it work without special "preparation" steps.
Allows useful programs with a minimal set of verbs. I think that you should be able to do many things while only needing to know assignment, a simple output statement, a simple determinent loop structure (for loop, not while loop), a simple decision statement for branching (if - else fits the bill). All the other fancy stuff can be left out until much later. Of course the programs will start out very linear (looping just goes back in the line and repeats stuff, and the branching skips lines you don't need at that time) but thats fine to start out.
A limited number of types. Strings and Numbers are all that is really necessary. It would even be nice if the language knew how to automatically convert numbers into strings and numerical strings into numbers but its not a requirement.
If you have a language that has extra features than those listed above I'd highly recommend "hiding" them until the learner has mastered what I have shown. Once they are at that point of mastry it shouldn't be too hard (though I have been surprised) to introduce concepts such as modularity by using functions and procedures, more complex branching and looping and a whole host of other things.
Visual basic forces you to worry about complex and crazy things like event sinks, graphical controls, and all that sort of glue.
I agree that once you understand how the computer works and how all the commands relate that its not that complicated. But back in the day where I knew very little about programming other than plain old BASIC and a bit of Pascal, Visual Basic confused the hell out of me. The biggest problem for me? Where the heck was the main loop, where did the program start, how did execution get from whereever that was to the part that I wrote? All the windows programming stuff was above my head.
If you have a real version of logo it had incredible string processing capability. Also I think its a functional language which is supposed to be a good way to get into properly understanding programming. The problem with many functional languages (lisp, schema and the like) is the syntax is ugly but if I remember correctly logo looks pretty decent on the screen.
Anyways my point is that logo is a real language and its useful for things other than "turtle" programming.
I am certain that references are not required for a turing complete language. A turing machine has nothing resembling references or pointers. So while PHP may be "broken" and make it more difficult to write complex programs effciently and elegantly, I'm sure it has the same power as any other turing complete language.
Depends on where you live. Self defence laws vary a lot from state to state. If you are interested in carrying a gun for protection I would advice talking to the local authorities and probably a local gun club for more information.
And this is MS's fault how? I fully agree that MS has made many security mistakes but I would say that a vast majority of security mistakes are made by the bozos setting up the boxes, and more by the users that access those boxes.
Its well known that the biggest security hole in any system is lack of knowledge and concern for secuity by the organization that uses and runs that system. Technology is definitely a part of that, but if the technology is misused even the best will be at risk.
I've avoided all but one of the big worms in the last 3 years by carefully configuring my PC and adding the proper external security to protect myself. I'm also careful where I browse and what attachements on e-mail I open. I also had my PC set to grab all critical updates so I got most of the patches before the worms were widespread. All of those same things are necessary on a *nix box are necessary to keep the script kiddies from scribbling "H4X0R5 R001" all over your websites (and sorry for my weak attempt at 1337 5934K or whatever they call it these days).
What the parent was pointing out (and I was hoping to see in here or I would have posted it myself) is that the installation REQUIRES you to PICK the password, and it forces an extra validation step if you CHOOSE blank.
Moreover, SQL authentication is no longer the default and the installer recommends you DO NOT ENABLE it. Because of this the default password for SQL 2000 is the NT credentials of the administrators of the box in question. It can be arugued that this is only as secure as the operating system, but its more secure than sa/ by a long shot.
So since you have given us the pattern to your users passwords you have reduced the password space on your server to 108 combinations? or am I missing something about having mutiple different results for the same start of sequence?
Its crazier than that, Google runs under the premise that switching out a machine is a large cost so they let the machine die and they may not get to it for months. The idea is to make thier system so overengineered that they don't spend very much maintaining it. As far as I can tell it works well for them.
The privacy fears come from the fact that Google has (up to this point at least) stated that they have no intention of deleting the indexed files after you sever your relationship with them. In Europe it is a requirement that you give users a right to opt out of a privacy infringing act and upon that opt out you obey it to the letter. I don't know that in general there is much to worry about but the letter of the law is clear.
Someone mentioned earlier that MS doesn't clean up right away (in fact the stated months which may well be accurate) but they do clean up the accounts the next time the server runs. In the future as privacy laws tighten that cleanup will have to happen more and more frequently which is where Google is getting pushback. The media is overblowing the facts by saying the issue is that they "read" the e-mail which is sort of beside the point, any clever indexing scheme "reads" the e-mail at that level.
You are entirely correct. The two go hand in hand, and I think sun is getting access to the authentication protocol as well as the directory protocol and vise versa to allow both operating systems to integerate with each other in an enterprise setting.
Thank you for the clarification, just shows you that you don't have to understand whats really going on to make windows work. (well technically I did understand whats going on, just disregarded the knowledge when writing my response.)
This raises the question for me of what is the difference of seeing something with your eyes and taking a picture of it. Isn't it the distribution of the pictures that makes the difference? If I am the only one that sees said picture then the camera is operating as memory enhancement of sorts.
That said I think that we should limit the distribution of the pictures taken and not the taking of them in the first place.
The key is to make it difficult enough and unsavory enough to crack software that the average person in your target audience won't go through the trouble to do it. That way you pretty much revenue from the product as you were going to get anyway, those that take the trouble to pirate it wouldn't buy it in the first place.
That said I'm excited at the prospect of being able to join a music subscription service (I use napster premium and its pretty cool) and have that subscription available to my portable player. That way I have music on demand any time any place, that would rock.
If someone could explain what makes this so groundbreaking maybe I'd have a better appreciation of it.
You could do what I did with my camera (if yours lets you, I had a Canon G3 and a G1 before that).
First manually set your focus and aperature to the hyperfocal (get rid of wasted time with autofocus and its pretty much what you want for indoor shooting anyway).
And second, take some test shots with flash and decide what ISO and flash setting was best (I think I could do flash compensation, I never played with that) and set those manually. While you are at it lock the white balance.
Lastly take all the pictures you want without the delay of all the "auto" features and know in advance that the camera is going to do more or less the right thing in the environment you are in.
The canon powershot G series (G1, G2, G3, G5, G6) all have decent burst modes that achieve multiple frames a second and they have an average price of around $500 (depending on which model you want). This requires you to anticipate the shots you want though. What always bothered me about my G1 and G3 was how long it took to shoot an unprepared (and non-focus locked) shot. Over a second for the camera to auto-focus and calculate white balance and exposure. You could get around this by locking focus and manually chosing white balance and exposure. Then it was about 2/3 a second to take the shot. Recovery time wasn't too hot either.
You failed to read the last article "How to Break The Rules" which gives hints as to why and how to go against the standard guildlines.
I also recommend browsing around the web starting at a good Digital Camera site. I managed to find some great info on shooting with digital cameras by doing this.
From the responses I've seen I think the sad truth is a rare few programmers have been formally trained in typing. If you had this article would sound completely ridiculous to you as well.
Automatic Update will be on by default, just wait for SP2.
That or they could do what people have been doing to record TV screens for ages and feed the camcorder a proper sync signal.
It may not be possible to get this respect and consideration from the managers where you work in which case you might need to look elsewhere.
On the other side of the coin more hours does not necessary mean more productivity. It may be fully possible to optimise your work time and priorities and manage to get all the work that needs to be done finished during normal hours and no need for extended periods of long hours.
I don't think there were really that many more injuries from guns (hunting excepted of course, a group of 6 or 8 drunk men with high powered rifles makes for a less than safe outing) than other states I've been in and read the news.
Anyways, BASIC isn't horrible to start with, the key is knowing what parts of your starting language still apply and what parts you should leave behind.
Maybe I'm a special case but I know many other incredible programmers that started programming in BASIC and have beautiful structured and OO code.
I get what you are going at, but along another different but related line, the problem may not be the language used but instead the teaching method being employed.
I've found that most people with even a small interest in programming (yes I've found some to where this won't apply) will understand how if you find the right approach to explaining it. The key is to start small and keep trying new ways to explain stuff until it sticks. The approach that worked well for me way back in the day was the BASIC programming book included with the TRS-80 color computer. If I were to attempt to teach someone to program I'd use that book as a model in the language of my choice.
Important features of a language to teach a beginner are:
If you have a language that has extra features than those listed above I'd highly recommend "hiding" them until the learner has mastered what I have shown. Once they are at that point of mastry it shouldn't be too hard (though I have been surprised) to introduce concepts such as modularity by using functions and procedures, more complex branching and looping and a whole host of other things.
Visual basic forces you to worry about complex and crazy things like event sinks, graphical controls, and all that sort of glue.
I agree that once you understand how the computer works and how all the commands relate that its not that complicated. But back in the day where I knew very little about programming other than plain old BASIC and a bit of Pascal, Visual Basic confused the hell out of me. The biggest problem for me? Where the heck was the main loop, where did the program start, how did execution get from whereever that was to the part that I wrote? All the windows programming stuff was above my head.
Anyways my point is that logo is a real language and its useful for things other than "turtle" programming.
I am certain that references are not required for a turing complete language. A turing machine has nothing resembling references or pointers. So while PHP may be "broken" and make it more difficult to write complex programs effciently and elegantly, I'm sure it has the same power as any other turing complete language.
Depends on where you live. Self defence laws vary a lot from state to state. If you are interested in carrying a gun for protection I would advice talking to the local authorities and probably a local gun club for more information.
And this is MS's fault how? I fully agree that MS has made many security mistakes but I would say that a vast majority of security mistakes are made by the bozos setting up the boxes, and more by the users that access those boxes.
Its well known that the biggest security hole in any system is lack of knowledge and concern for secuity by the organization that uses and runs that system. Technology is definitely a part of that, but if the technology is misused even the best will be at risk.
I've avoided all but one of the big worms in the last 3 years by carefully configuring my PC and adding the proper external security to protect myself. I'm also careful where I browse and what attachements on e-mail I open. I also had my PC set to grab all critical updates so I got most of the patches before the worms were widespread. All of those same things are necessary on a *nix box are necessary to keep the script kiddies from scribbling "H4X0R5 R001" all over your websites (and sorry for my weak attempt at 1337 5934K or whatever they call it these days).
What the parent was pointing out (and I was hoping to see in here or I would have posted it myself) is that the installation REQUIRES you to PICK the password, and it forces an extra validation step if you CHOOSE blank.
Moreover, SQL authentication is no longer the default and the installer recommends you DO NOT ENABLE it. Because of this the default password for SQL 2000 is the NT credentials of the administrators of the box in question. It can be arugued that this is only as secure as the operating system, but its more secure than sa/ by a long shot.
So since you have given us the pattern to your users passwords you have reduced the password space on your server to 108 combinations? or am I missing something about having mutiple different results for the same start of sequence?
Or put in one of those noise canceling devices they use for loud office buildings :)
Its crazier than that, Google runs under the premise that switching out a machine is a large cost so they let the machine die and they may not get to it for months. The idea is to make thier system so overengineered that they don't spend very much maintaining it. As far as I can tell it works well for them.
Someone mentioned earlier that MS doesn't clean up right away (in fact the stated months which may well be accurate) but they do clean up the accounts the next time the server runs. In the future as privacy laws tighten that cleanup will have to happen more and more frequently which is where Google is getting pushback. The media is overblowing the facts by saying the issue is that they "read" the e-mail which is sort of beside the point, any clever indexing scheme "reads" the e-mail at that level.
Thank you for the clarification, just shows you that you don't have to understand whats really going on to make windows work. (well technically I did understand whats going on, just disregarded the knowledge when writing my response.)
That said I think that we should limit the distribution of the pictures taken and not the taking of them in the first place.
That said I'm excited at the prospect of being able to join a music subscription service (I use napster premium and its pretty cool) and have that subscription available to my portable player. That way I have music on demand any time any place, that would rock.