I learned Boolean Algebra for a CS degree. The application the University intended for its use was for designing hardware circuits.
As a programmer, over the years I have had many cases where I had to write programs that did different things based on a list of inputs and their values. My knowledge of Boolean Algebra has helped me make the code simpler because I could reduce the input values to the lowest equivalent. My resulting code therefore has less conditionals (if..then..else and switch statements).
If someone talking about security starts to mention ROI, I tune them out. They don't know the basics about security.
When I talk security to upper management I never use the term ROI. That term is too steeped in revenue generation that you cannot separate the term from the expectation of increased sales or increased profitability.
Security is like insurance it protects against loss. Security (for almost all companies) never generates revenue, therefore it can never have ROI in the traditional sense.
Some security companies will try to say that the Return is [insert some intangible benefit here].
They should really sell it like insurance where they mention the protection from loss in tangible terms.
This is called a SQL Injection security hole. You can write it in practically any language that connects to a database.
Capability Sniffing does not work in all cases.
on
DHTML Utopia
·
· Score: 1
No browser sniffing. This aims to future-proof code by testing for features rather than sniffing for browser name and version. So, before using the TimeTravelCureCancer method, the current browser is tested to see whether it's supported. If it is, the script continues. If it isn't,the script silently fails with graceful degradation.
Here is an example that I ran into of how capability sniffing is not enough:
The add method on a select element exists in IE 6 as well as Firefox. However, in order to add an option element to the end of the select element's list, you need to do this in IE:
Slashdot Mirror
I learned Boolean Algebra for a CS degree. The application the University intended for its use was for designing hardware circuits.
As a programmer, over the years I have had many cases where I had to write programs that did different things based on a list of inputs and their values. My knowledge of Boolean Algebra has helped me make the code simpler because I could reduce the input values to the lowest equivalent. My resulting code therefore has less conditionals (if..then..else and switch statements).
I wonder if they purchased performance rights through BMI. If not, will the RIAA come down hard on ThinkGeek?
If someone talking about security starts to mention ROI, I tune them out. They don't know the basics about security.
When I talk security to upper management I never use the term ROI. That term is too steeped in revenue generation that you cannot separate the term from the expectation of increased sales or increased profitability.
Security is like insurance it protects against loss. Security (for almost all companies) never generates revenue, therefore it can never have ROI in the traditional sense.
Some security companies will try to say that the Return is [insert some intangible benefit here].
They should really sell it like insurance where they mention the protection from loss in tangible terms.
ResultSet readFromDatabase(String userInput)
{
String sql = "select * from users where userid = " + userInput;
PreparedStatement psMyStatement = connMyConnection.prepareStatement(sql);
ResultSet rsResults = psMySQLStatement.executeQuery();
return rsResults;
}
This is called a SQL Injection security hole. You can write it in practically any language that connects to a database.
The add method on a select element exists in IE 6 as well as Firefox. However, in order to add an option element to the end of the select element's list, you need to do this in IE:
And this in Firefox:
References:
MSDN Reference
DOM Reference