I'm always interested when I see Massachusetts called Tax-achusetts. The overall tax burden on MA residents (10.1%) is only slightly above the national average (10.0%). You never hear of "Taxes" (10.9%), "Utax" (11.1%), "New Taxico" (12.0%), or "Louisi-assess" (13.0%).
I live in Colorado, and the tax burden for CO residents is below average (9.5%), but we cannot fund all of the new unfunded mandates from the new "debt and spend" ruling party.
Brining this back on topic, I'd welcome an OpenDoc initiative in this state to help reduce spending. There are a ton of things I'd rather we spend our public tax dollars on than the MSFT tax.
Lying about extra-marital sex is done on a regular basis by men and women all across our great country every day. It's as quintessentially American as Mom and Apple Pie.
You'll notice also that this does nothing to improve the security of the code. It just makes it more expencive.
This is only superficially true. A side effect of the insurance industry on many industries is that best practices are developed and enforced in order to reduce insurance rates. As the actuarial for programming evolves, programmers (or the companies which employ them) will be encouraged to following practices that produce better code in order to lower their insurance rates. The cost of not following those practices are currently not well enough quantified for management to base a decision one way or another.
Don't allow it to turn into a pissing contest. Make it a negotiation. "This feature will cost you X $ and Y weeks of development." Let them decide. Make sure your quote is for the time required to get it done right. Features, cost and quality are the three main variables in development. Don't compromise on quality. (It's your group that deals with the after-effects of poor quality after all.) But make your quality goals reasonable for the business. You get to set the time/cost per feature. The customer gets to determine the features.
Have the customer sign off on the requirements. Anything not listed in the doc doesn't get implemented until the next enhancement cycle unless they are completely willing to renegotiate everything.
Don't waver in these negotiation points. Development time & costs are negotiable -- and 100% dependent on the feature set. It's really tough to get into a pissing contest when the rules are that clear.
You also need properly trained personnel who can spot security flaws in code. Those are typically expensive and harder to hire than your average coder or QA person. If said company is only willing to pay an "average" salary, they will get exactly what they pay for.
By propagating ideologically inspired amoral theories, business schools have actively freed their students from any sense of moral responsibility.
But you should read the article in full. It presents the reader with a good deal of information about how business and ecomonics is taught, and how this affects corporate behavior and governance. This is an academic article and the writing style is typical of most academic writing, dry and constantly interrupted with references and citations. A more condensed version, edited for the for the lay person, would be most welcome. The fundamental ideas expressed within this article deserves a far greater audience.
You're speaking out your ass: Most places that store login information encrypt it before it hits the database.
Don't be insulting, young grasshoppa. Your severe lack of clue shows it is not your place. Most places isn't good enough. I ordered something online recently with a credit card. Had to create an account with a password. Got a nice confirmation email back telling me, in plain text, how to log back in to their system. My password went through how many networks and mail servers in clear text on that one?
No... (and it's obvious you know this already) they want people to watch the advertisements.
The problem is that the way all of the deals are structured within the entertainment industry (exclusive rights, release schedules), it is very hard to introduce new methods of timely legal content delivery.
I am not sure why you believe RPM is Redhat-centric. There are lots of RPM-based distributions, many of which are not direct decendants of Red Hat. I don't know that one can say the same of.deb format. From my vantage point it seems like.deb-based distributions are a big part of the problem. But, more to the point, having major distributions using incompatible package formats is certainly hurting the standards process.
Seriously, you need to work with someone who has a clue. Anyone reviewing these scans should know what they are looking at. If they don't, they have no room to criticize. It is the security consultants job to put the scan and the vulnerabilities in context. They need to explain the risks to management in a manner that management can understand. Their report should come with recommendations on how to correct the problems, and it should at least try to outline the consequences of the fixes. The consultants should have worked with the engineering/admin team to understand the holes before the report went to management. Otherwise you paid for a whole lot of nothing.
The first remotely-controlled non-stop circumnavigation. And the first autonomous non-stop 'round the world trip. Both will happen in my lifetime. I actually think the former is harder than the latter, unless one has Milstar at their disposal.
Funny thing is, Java EJBs are CORBA. They communicate over IIOP. You can generate CORBA IDL for them. And you can connect a CORBA client to them. CORBA isn't "due any day" -- it's here.
Those who know history (esp. of distributed object systems) are watching SOAP and "Web Services" evolve and just laughing our asses off (or crying, depending on the situation). CORBA has been simplifying while SOAP has been complexifying. SOAP is now more complicated to develop for than CORBA.
Well, that's nice. But most of the civilized world does not run a distribution that ships with Gnome 2.8.1. My rather modern (4-month old) Fedora Core Mark III has not released anything past 2.8.0. It was a really *stupid* oversight on the part of the Gnome development team. But they've been on a real "lets piss off the power user" binge for quite a while.
The parent did not deserve to be modded up as "informative". An accurate title for the post would be "Python is not statically typed."
Python is a strongly typed language. It is in the class of strongly- and dynamically-typed languages. Read this article on Python's type system for a good overview and a little information on "type" terminology.
Slashdot Mirror
Offtopic??? Unfunny, I could see -- if you've had your sense of humor surgically removed. Read the cards in their hat brims.
I hope whoever modded this offtopic gets run over by a Mack truck in metamoderation.
Did the lobbyists look anything like this? http://www.ucomics.com/foxtrot/2005/10/31/
I'm always interested when I see Massachusetts called Tax-achusetts. The overall tax burden on MA residents (10.1%) is only slightly above the national average (10.0%). You never hear of "Taxes" (10.9%), "Utax" (11.1%), "New Taxico" (12.0%), or "Louisi-assess" (13.0%).
I live in Colorado, and the tax burden for CO residents is below average (9.5%), but we cannot fund all of the new unfunded mandates from the new "debt and spend" ruling party.
Brining this back on topic, I'd welcome an OpenDoc initiative in this state to help reduce spending. There are a ton of things I'd rather we spend our public tax dollars on than the MSFT tax.
Lying about extra-marital sex is done on a regular basis by men and women all across our great country every day. It's as quintessentially American as Mom and Apple Pie.
This is only superficially true. A side effect of the insurance industry on many industries is that best practices are developed and enforced in order to reduce insurance rates. As the actuarial for programming evolves, programmers (or the companies which employ them) will be encouraged to following practices that produce better code in order to lower their insurance rates. The cost of not following those practices are currently not well enough quantified for management to base a decision one way or another.
You have business analysts?!? You lucky devil.
Don't allow it to turn into a pissing contest. Make it a negotiation. "This feature will cost you X $ and Y weeks of development." Let them decide. Make sure your quote is for the time required to get it done right. Features, cost and quality are the three main variables in development. Don't compromise on quality. (It's your group that deals with the after-effects of poor quality after all.) But make your quality goals reasonable for the business. You get to set the time/cost per feature. The customer gets to determine the features.
Have the customer sign off on the requirements. Anything not listed in the doc doesn't get implemented until the next enhancement cycle unless they are completely willing to renegotiate everything.
Don't waver in these negotiation points. Development time & costs are negotiable -- and 100% dependent on the feature set. It's really tough to get into a pissing contest when the rules are that clear.
You also need properly trained personnel who can spot security flaws in code. Those are typically expensive and harder to hire than your average coder or QA person. If said company is only willing to pay an "average" salary, they will get exactly what they pay for.
This would be moderated +5 by now if there were a "+1 Sad, But True" moderation option.
Trust me -- terraforming any of the planets in our solar system is going to be cheaper than that.
But you should read the article in full. It presents the reader with a good deal of information about how business and ecomonics is taught, and how this affects corporate behavior and governance. This is an academic article and the writing style is typical of most academic writing, dry and constantly interrupted with references and citations. A more condensed version, edited for the for the lay person, would be most welcome. The fundamental ideas expressed within this article deserves a far greater audience.
This is why I continue to read Slashdot. Kudos to whomever is responsible for that. You made my day!
Don't be insulting, young grasshoppa. Your severe lack of clue shows it is not your place. Most places isn't good enough. I ordered something online recently with a credit card. Had to create an account with a password. Got a nice confirmation email back telling me, in plain text, how to log back in to their system. My password went through how many networks and mail servers in clear text on that one?
It only takes one idiot to ruin everyone's day.
When I read House Passes Spyware Bills the first question that popped into mind was "OK, how many will we be required to install"?
No... (and it's obvious you know this already) they want people to watch the advertisements.
The problem is that the way all of the deals are structured within the entertainment industry (exclusive rights, release schedules), it is very hard to introduce new methods of timely legal content delivery.
I am not sure why you believe RPM is Redhat-centric. There are lots of RPM-based distributions, many of which are not direct decendants of Red Hat. I don't know that one can say the same of .deb format. From my vantage point it seems like .deb-based distributions are a big part of the problem. But, more to the point, having major distributions using incompatible package formats is certainly hurting the standards process.
Linux: copyrighted "software program", and "not commercially released".
Doh!
Can you see me now?
Good!
The dead cat??? You must be living in an alternate universe!
Seriously, you need to work with someone who has a clue. Anyone reviewing these scans should know what they are looking at. If they don't, they have no room to criticize. It is the security consultants job to put the scan and the vulnerabilities in context. They need to explain the risks to management in a manner that management can understand. Their report should come with recommendations on how to correct the problems, and it should at least try to outline the consequences of the fixes. The consultants should have worked with the engineering/admin team to understand the holes before the report went to management. Otherwise you paid for a whole lot of nothing.
Dude, typing "sell" requires just way too much effort.
The project is late because I spend half of my day filling out TPS reports, and making sure they have the right cover sheet on them.
The first remotely-controlled non-stop circumnavigation. And the first autonomous non-stop 'round the world trip. Both will happen in my lifetime. I actually think the former is harder than the latter, unless one has Milstar at their disposal.
Funny thing is, Java EJBs are CORBA. They communicate over IIOP. You can generate CORBA IDL for them. And you can connect a CORBA client to them. CORBA isn't "due any day" -- it's here.
Those who know history (esp. of distributed object systems) are watching SOAP and "Web Services" evolve and just laughing our asses off (or crying, depending on the situation). CORBA has been simplifying while SOAP has been complexifying. SOAP is now more complicated to develop for than CORBA.
Well, that's nice. But most of the civilized world does not run a distribution that ships with Gnome 2.8.1. My rather modern (4-month old) Fedora Core Mark III has not released anything past 2.8.0. It was a really *stupid* oversight on the part of the Gnome development team. But they've been on a real "lets piss off the power user" binge for quite a while.
Python is a strongly typed language. It is in the class of strongly- and dynamically-typed languages. Read this article on Python's type system for a good overview and a little information on "type" terminology.