Ahem. While this problem is prevalent in PHP/ASP(AFAIK pre.NET) code, it is long gone in most "sane" languages.
If you follow elementary "safe" coding conventions in Perl, Python or Ruby and use prepare() statements it is nearly impossible to write injectable code. I am saying "nearly" because there will always be an inventive idiot to write a code which can allow injection in any language.
Ahem! This problem exists in all languages. It's bad programmers that cause the problem. the Prepare() method is part of the NewADOConnection() class in PHP as well and is followed as "safe" practice. Bad programmers don't use it.
Intel had bit of an advertising coup in that any advert on TV for a company selling PCs (at least in the UK) seemed to have an "Intel inside" logo and jingle played during each ad.
... and changing even a small piece of code often requires changing a lot of tests. If you can offer any suggestions about how to improve that, I'm all ears.
That's the wrong way round. Shouldn't you be rewriting the tests to conform to the new specifications then changing the code for the re-written tests that fail? Doing it your way will make it very difficult to trace code.
Another way of pair programming could be to have one person writing the tests and one writing the code.
Now that you get GUI editors that not only auto-complete code, but know about the classes within the application you are developing and can correct method calls and parameter types who the hell would use VI to write code?
Rapid Application Development VI is not.
I suspect that there is a little bit of protectionism going on, in that, to the lay person, watching an IT boffin do stuff in VI looks "impressive" and makes the develper look like they are doing something difficult.
In my applcations, I always think, if a lay person is able to work out what my code does, then I've done my job as far as well-written code goes. Code should be easy to read, easy to correct and damn near obvious what it does. Using vi for programming obfuscates code and is used by those unwilling to move on.
The only time vi should be used is if you are editing config or other admin files on a server when using telnet which should be damn close to never, on a live box at least.
They haven't hi-jacked anything, unless it's possible to hi-jacked their own domain.
They won't stop companies from registering their own.cm domains, in-fact, I am presuming the aim of their actions is to encourage people to register their domain as a.cm domain.
Slashdot Mirror
Ahem! This problem exists in all languages. It's bad programmers that cause the problem. the Prepare() method is part of the NewADOConnection() class in PHP as well and is followed as "safe" practice. Bad programmers don't use it.
Intel had bit of an advertising coup in that any advert on TV for a company selling PCs (at least in the UK) seemed to have an "Intel inside" logo and jingle played during each ad.
I never saw an "AM2 inside" equivalent.
That's the wrong way round. Shouldn't you be rewriting the tests to conform to the new specifications then changing the code for the re-written tests that fail? Doing it your way will make it very difficult to trace code.
Another way of pair programming could be to have one person writing the tests and one writing the code.
You should have coding standards in place where that kind of thing is sorted out before coding starts anyway.
Things like the command line interface, wrapping code and adding control characters make code more difficult to read.
Surely you mean saves you having to write code that is required, but pretty bog standard, like the basic structure of a class definition etc...
Now that you get GUI editors that not only auto-complete code, but know about the classes within the application you are developing and can correct method calls and parameter types who the hell would use VI to write code?
Rapid Application Development VI is not.
I suspect that there is a little bit of protectionism going on, in that, to the lay person, watching an IT boffin do stuff in VI looks "impressive" and makes the develper look like they are doing something difficult.
In my applcations, I always think, if a lay person is able to work out what my code does, then I've done my job as far as well-written code goes. Code should be easy to read, easy to correct and damn near obvious what it does. Using vi for programming obfuscates code and is used by those unwilling to move on.
The only time vi should be used is if you are editing config or other admin files on a server when using telnet which should be damn close to never, on a live box at least.
You can change any of the groups of people for any other group of people. It doesn't matter. It will always be relevant.
"That's the whole point, Diebold: you shouldn't have to "follow proper procedures." The machines should make it impossible to do so ..."
..." ;)
Don't you mean, "... The machines should make it impossible not to do so
They haven't hi-jacked anything, unless it's possible to hi-jacked their own domain. They won't stop companies from registering their own .cm domains, in-fact, I am presuming the aim of their actions is to encourage people to register their domain as a .cm domain.