This is a failure on your part. Bean counters are not penny-wise, pound foolish. They do need a concrete financial analysis, however, to prove that you aren't just blowing smoke up their skirt.
Because most of the time, programmers are doing just that.
And also, programmers often fail to understand the cost of money and that sometimes it is better spend more tomorrow than a little bit today.
Huh? enStratus and just about every other infrastructure management tool performs auto-scaling. It's a baseline feature, and you need tools like enStratus to do auto-scaling for you since Amazon does not (currently) support auto-scaling.
It's 4pm on a Saturday and chances are that your site is being hit hard either because you were being an idiot or because someone is engaged in an attack on you.
If you plan properly, there are no sudden 4pm on Saturday spikes in traffic.
That's a very poorly thought out view of a cloud infrastructure.
With Amazon in particular, you do have SLAs and you can easily design an infrastructure that will be very secure for most organizational needs and exceed the SLAs offered by Amazon.
In my experience, people without a college degree and technology are worthless. And, unfortunately, I have more experience in that arena than I would like.
Any new technology is initially going to be affordable only by the wealthy. If we say we are not going to subsidize R&D for products for the wealthy, we are saying we are not going to subsidize R&D at all.
Seriously, SQL Injection is one of the simplest attack vectors to prevent. If you can't prevent SQL injection, you should not be allowed to write a web application.
Goodwill only shows up on the balance sheet when an acquisition or some similar event occurs which creates a discrepancy between the purchase amount and the balance sheet of the acquisition.
You don't just make up a number and add it onto your balance sheet.
No, I am making an educated judgment based on many years dealing different programming languages and a solid understanding of the programming paradigm on which Perl is based.
Perl is based on the idea that there are many ways to express the same programming concept. That is a useful philosophy in support of UNIX sys admins that quickly need to hack together scripts to perform various thankless tasks. Funnily enough, that's why Perl was created in the first place.
However, that is a terrible philosophy for supporting enterprise-level business applications. You see, the problem with have multiple ways to express things means that only experts will fully understand all ways to express things, thus making even well written code difficult for non-experts to maintain unless the chosen programming paradigm matches their thinking. Worse, this philosophy actively encourages poor programming habits.
I have always said that you have to be an expert Python programmer to write hard to maintain Python code; you have to be an expert Perl programmer to easy to maintain Perl code.
The laws are actually very unclear on the issue of IT workers.
If it was important to the workers, they should have negotiated for the status prior to being hired.
You can't take advantage of being an exempt employee for years and then come back and say, "By the way, I want the benefits of being non-exempt as well."
I'm sorry, but just where and when was "God created the heavens and the earth" refuted?
The same place where "A big ass ham sandwiched shat a load of mayonaise and, behold, the world was alive," was refuted.
In other words, you don't prove a negative. But you can recognize that there is absolutely no evidence AT ALL for either assertion and, furthermore, that each assertion is terribly fantastic and requires a significant level of support before it should even be considered.
I am not sure how old the patent is, but any mud from the late 80's/early 90's would have had a feature that let users indicate things they would like to see and store it in a database.
Slashdot Mirror
This is a failure on your part. Bean counters are not penny-wise, pound foolish. They do need a concrete financial analysis, however, to prove that you aren't just blowing smoke up their skirt.
Because most of the time, programmers are doing just that.
And also, programmers often fail to understand the cost of money and that sometimes it is better spend more tomorrow than a little bit today.
Huh? enStratus and just about every other infrastructure management tool performs auto-scaling. It's a baseline feature, and you need tools like enStratus to do auto-scaling for you since Amazon does not (currently) support auto-scaling.
enStratus has that feature.
No, the argument is that auto-scaling, upon close examination, has very few benefits that are not actually better realized through other mechanisms.
It's 4pm on a Saturday and chances are that your site is being hit hard either because you were being an idiot or because someone is engaged in an attack on you.
If you plan properly, there are no sudden 4pm on Saturday spikes in traffic.
That's a very poorly thought out view of a cloud infrastructure.
With Amazon in particular, you do have SLAs and you can easily design an infrastructure that will be very secure for most organizational needs and exceed the SLAs offered by Amazon.
Congrats. You are the exception, not the rule.
In my experience, people without a college degree and technology are worthless. And, unfortunately, I have more experience in that arena than I would like.
It's a cynical way of saying that completing college shows you are capable of taking on something and seeing it through to completion.
And it's absolutely true. Absent seriously special circumstances, I would not consider hiring someone without a college degree.
Any new technology is initially going to be affordable only by the wealthy. If we say we are not going to subsidize R&D for products for the wealthy, we are saying we are not going to subsidize R&D at all.
And if you can be sued, as a startup, it's game over. And no one will invest you because of the cloud of a lawsuit.
Seriously, SQL Injection is one of the simplest attack vectors to prevent. If you can't prevent SQL injection, you should not be allowed to write a web application.
Goodwill only shows up on the balance sheet when an acquisition or some similar event occurs which creates a discrepancy between the purchase amount and the balance sheet of the acquisition.
You don't just make up a number and add it onto your balance sheet.
Tomcat + JSP + JDBC to MySQL
Everything else except desktop apps build on that foundation.
Nightmare LPMud about 10 years had persistent changes, even to the point that the main town was eventually destroyed by warfare.
It is doable, it just takes a hell of a lot of planning into a larger story line, including "what if" scenarios.
No, I am making an educated judgment based on many years dealing different programming languages and a solid understanding of the programming paradigm on which Perl is based.
Perl is based on the idea that there are many ways to express the same programming concept. That is a useful philosophy in support of UNIX sys admins that quickly need to hack together scripts to perform various thankless tasks. Funnily enough, that's why Perl was created in the first place.
However, that is a terrible philosophy for supporting enterprise-level business applications. You see, the problem with have multiple ways to express things means that only experts will fully understand all ways to express things, thus making even well written code difficult for non-experts to maintain unless the chosen programming paradigm matches their thinking. Worse, this philosophy actively encourages poor programming habits.
I have always said that you have to be an expert Python programmer to write hard to maintain Python code; you have to be an expert Perl programmer to easy to maintain Perl code.
And that makes all the difference in the world.
Python is the best language on Earth to use for "pseudo-code" in low-level requirements.
I love all of this bashing business for not using Perl as if somehow not using a technology that some geeks think is cool matters to business.
What matters to business is the cost of maintaining a system, and Perl software is generally way too complex to maintain. And that means costly.
The combined with the fact that companies are moving away from maintaing custom software at all, it is not surprising Perl is on the downswing.
Given that your employer owns your inventions that you make while employed, you have absolutely no business refusing.
Why do people look to randomness for "free will"?
There is simply no meaningful concept of free will you would actually want to have.
Is the idea of a random event being the source of your "will" a concept that makes you think, "Hey! That action was MINE!"?
Why would any employer actually opt to offer you salary as a non-exempt employee?
The laws are actually very unclear on the issue of IT workers.
If it was important to the workers, they should have negotiated for the status prior to being hired.
You can't take advantage of being an exempt employee for years and then come back and say, "By the way, I want the benefits of being non-exempt as well."
NBC mentioned they were fake when the ceremony was being broadcast.
This is a serious non-story.
I'm sorry, but just where and when was "God created the heavens and the earth" refuted?
The same place where "A big ass ham sandwiched shat a load of mayonaise and, behold, the world was alive," was refuted.
In other words, you don't prove a negative. But you can recognize that there is absolutely no evidence AT ALL for either assertion and, furthermore, that each assertion is terribly fantastic and requires a significant level of support before it should even be considered.
System administration is where MySQL kills PostgreSQL.
You have to have a DBA for PostgreSQL, you don't for MySQL.
I am not sure how old the patent is, but any mud from the late 80's/early 90's would have had a feature that let users indicate things they would like to see and store it in a database.
It's called a feature request database.
I am sure there are other examples.