What happens if you need to patch or upgrade in a few years? Like for security? Do you have to rely on unsupported frameworks or throw everything away and start over? How does it work?
Remember, companies pay huge licensing fees exactly for support.
Water vapor is pretty good at it, though saturation and rain buffers some of it. But you get a feedback loop; higher temps increase evaporation which the raises temperature, etc. It's the feedback that makes it difficult.
I do get your point. But part of the problem is that there doesn't seem, at least in my experience, any provision made for slippage. Every release and/or sprint is filled to the bursting point with features. In disciplines like Operations Research the rule is to never fill the work queue greater than 75% [1]. Otherwise if anything goes wrong you're hosed. Managers want maximum productivity but the only only way to get that is through scheduling in extra capacity. which to most managers seems inefficient, so they cram in more work and ensure failure.
And I do believe we should label things as failures. By not doing so we come to think all things went well and we don't have to think about what we are doing. While a failure would cause an analysis of what went wrong and what needs to be fixed.
[1] Which is about the effective saturation point in ethernet.
But what offends me is the lie, "We made the deadline". No, no you didn't. You fudged the situation and pretended that you achieved something. When you didn't. Which allows arbitrary deadlines to exist without onus or learning what worked. Very unscientific.
Do you get it? Instead of saying "We failed" and then looking for reasons continued failure is ensured and no improvement occurs.
We never achieve them anyway. It normally starts out as, "We need to deliver a high quality product with A,B,C,D,E,F,G,H by the deadline." Then it goes:
But we can't do D due to a defect in the vendors/open source project's libraries.
The deadline is slipping so we talked the customer into deferring the release of E until the next release.
Oops C relies on D so we can't ship that.
Chris and Bob quit so we are even more short handed than before.
G is experiencing massive scope creep, let's cut capabilities so we can ship it.
We're more short handed than ever so we can't fix more than critical bugs.
The QA automation is falling behind due to all the changes so we'll have to test manually.
So what get's shipped often looks nothing like what was promised. All that happens is the goal post is moved and victory is declared.
HP is doing the right thing by disabling the battery and recalling the the defective. Instead of stone walling, denying a problem, or shifting the blame. What has the world come to?
Looking at programming languages is good but this report implies there are other factors more important at play. What is the demographic of a good programmer? What is the marker of a good programmer who does not produce bugs? Ivy league vs. "Scheme certificate in 90 days" training programs? Wyoming programmers vs. California programmers? Just graduated 20 somethings vs. 50 year olds? Traditional CS programs vs. explicit software development training programs?
We all have our biases, but let's see what, if anything, pops up.
"Yet here we are 20 years later with a full employment economy. "
How many of those jobs are sub-poverty level? Has the middle class been increasing or shrinking. There is evidence that we are looking at an economic crisis brewing. Looking at jobs alone is just as stupid as only looking at GDP.
It was about serving casinos. Because that's what Vegas is about (I learned a lot when I lived there). Basically, if you understand a carnival midway, you understand the strip.
Slashdot Mirror
Just how corporate management works. Got it. along with bungee managers, bungee programmers.
So you can achieve bug compliance with V1.0?
What happens if you need to patch or upgrade in a few years? Like for security? Do you have to rely on unsupported frameworks or throw everything away and start over? How does it work?
Remember, companies pay huge licensing fees exactly for support.
how do you know your simulator is correct?
whoosh
like drop it into some bonds or something and earn some non-refundable money from it.
You sound like like you are an experienced sysadmin /s
If management went cheap on backups and recovery, they're screwed
If it was "cloudified" depending on TOS they could screwed royally. Sorry backups and recovery aren't in the TOS (Terms of Shit).
If they cut costs and hired monkeys to run the thing they are screwed. See also outsourced it, see also cloudified.
This is more than a glitch as you so glibly put it, train it is a wreck.
It's big because money goes in and none comes out.
Which is backed by FDIC and private insurance.
Water vapor is pretty good at it, though saturation and rain buffers some of it. But you get a feedback loop; higher temps increase evaporation which the raises temperature, etc. It's the feedback that makes it difficult.
No original data were presented, from what I could see.
https://www.skepticalscience.c...
I do get your point. But part of the problem is that there doesn't seem, at least in my experience, any provision made for slippage. Every release and/or sprint is filled to the bursting point with features. In disciplines like Operations Research the rule is to never fill the work queue greater than 75% [1]. Otherwise if anything goes wrong you're hosed. Managers want maximum productivity but the only only way to get that is through scheduling in extra capacity. which to most managers seems inefficient, so they cram in more work and ensure failure.
And I do believe we should label things as failures. By not doing so we come to think all things went well and we don't have to think about what we are doing. While a failure would cause an analysis of what went wrong and what needs to be fixed.
[1] Which is about the effective saturation point in ethernet.
But what offends me is the lie, "We made the deadline". No, no you didn't. You fudged the situation and pretended that you achieved something. When you didn't. Which allows arbitrary deadlines to exist without onus or learning what worked. Very unscientific.
Do you get it? Instead of saying "We failed" and then looking for reasons continued failure is ensured and no improvement occurs.
Or a blatant failure to fix re: Intel
We never achieve them anyway. It normally starts out as, "We need to deliver a high quality product with A,B,C,D,E,F,G,H by the deadline."
Then it goes:
But we can't do D due to a defect in the vendors/open source project's libraries.
The deadline is slipping so we talked the customer into deferring the release of E until the next release.
Oops C relies on D so we can't ship that.
Chris and Bob quit so we are even more short handed than before.
G is experiencing massive scope creep, let's cut capabilities so we can ship it.
We're more short handed than ever so we can't fix more than critical bugs.
The QA automation is falling behind due to all the changes so we'll have to test manually.
So what get's shipped often looks nothing like what was promised. All that happens is the goal post is moved and victory is declared.
HP is doing the right thing by disabling the battery and recalling the the defective. Instead of stone walling, denying a problem, or shifting the blame. What has the world come to?
Looking at programming languages is good but this report implies there are other factors more important at play. What is the demographic of a good programmer? What is the marker of a good programmer who does not produce bugs? Ivy league vs. "Scheme certificate in 90 days" training programs? Wyoming programmers vs. California programmers? Just graduated 20 somethings vs. 50 year olds? Traditional CS programs vs. explicit software development training programs?
We all have our biases, but let's see what, if anything, pops up.
Brought to you by assorted TLA institutions, various other agencies, Facebook, Amazon, Slashdot, twitter, Google, etc.
As well as history's greatest mis-information matrix.
SOmething to consider.
"Yet here we are 20 years later with a full employment economy. "
How many of those jobs are sub-poverty level? Has the middle class been increasing or shrinking. There is evidence that we are looking at an economic crisis brewing. Looking at jobs alone is just as stupid as only looking at GDP.
*Yet here we are 20 years later with a full employment economy.
But to board it you ahve to go past slots, gaming tables, etc. Get it?
Missed 23rd by this much...
It was about serving casinos. Because that's what Vegas is about (I learned a lot when I lived there). Basically, if you understand a carnival midway, you understand the strip.
+1
They had their Software Engineers do it. Because all Engineers are interchangeable, right?