3,255 karma · joined July 20, 2015
There's a lot of empirical research about this. A. Lot. Starting in the 80's, even. It's as close as it gets to empirically proven that software testing greatly reduces bugs and regressions, and accelerates delivery over the long term. It's not as clear if the acceleration is entirely freed up resources that would otherwise be spent fixing bugs, or if it also makes people develop faster. Also, it's pretty clear that Automated testing doesn't accelerate short or short term projects.
So what gives? Why do users in your circle regret it? And where does the vr community hang out, so I can learn more?
Can someone knowledgeable help me understand why these concepts seem missing from financial market penalties like this? The same people still have their license, and probably didn't even suffer a loss on the activity.
"Intel GVT-g is a full GPU virtualization solution with mediated pass-through (VFIO mediated device framework based), starting from 5th generation Intel Core(TM) processors with Intel Graphics processors. GVT-g supports both Xen and KVM (a.k.a XenGT & a.k.a KVMGT). A virtual GPU instance is maintained for each VM, with part of performance critical resources directly assigned. The capability of running native graphics driver inside a VM, without hypervisor intervention in performance critical paths, achieves a good balance among performance, feature, and sharing capability."
I encourage you to look at the numbers for yourself. The equivalent baseload power technologies are all WAY more dangerous.
Go and tally up the human casualties from nuclear over its entire history. Use the most damning numbers you can possibly find. Go ahead and include the victims of Hiroshima and Nagasaki if you like. Include any count of potential cancer cases too. Even using the most biased, openly political casualty counts you can find, it is challenging to get to 1.5 million over the entire history of the power source. If you stick to relatively credible sources you'll certainly be below half a million.
Now look at the human casualties from coal when it's working properly. No accidents, just regular power production. The first duckduckgo result for me estimates about 8.7 million deaths per year, not including accidents, bombs, or non fatal casualties.
The casualty rate from nuclear's entire history doesn't even approach the death rate from coal, oil, or gas in a single year.
> nuclear waste
One person lifetime of electricity creates about 350ml (about a coke can) of solid nuclear waste. We know where that waste is, and what it is doing. We can monitor and control access and keep people away from it.
In contrast, one person lifetime of coal power produces hundreds of thousands of TONS of waste, much of which is also radioactive, but lets not forget about the toxic heavy metals and carbon. Most of that waste goes into the atmosphere, where it cannot be tracked or controlled at all, and where it causes millions of deaths per year. To be fair a lot of it goes into the water and ground, too.
The fact that there are options AT ALL for nuclear waste puts it miles ahead of the competition.
Nuclear is by far the lowest carbon, safest, lowest waste universally available baseload power source ever invented. Casualties from nuclear aren't even a rounding error compared to the alternatives on the table.
You are absolutely right however, that it is highly volatile politically.
https://www.statista.com/statistics/494425/death-rate-worldw... is a nice reference for easy comparison, but really, duckduckgo it yourself.
What makes more sense for you will depend on your workload and scaling requirements.
Much more accurate are estimates of difficulty or complexity (small medium large, weighted numbers, whatever). The manager can then make an average conversion rate to time (with error bars), and use that for medium/long term forecasting. This is demonstrated extremely accurate compared to time estimation (but it is useless and breaks if you apply time/points pressure to your team, or even let them think in terms of a time conversion rate).
This is not new research. Kahneman's Nobel prize about decisions under uncertainty was in 2002. Put away the superstitions and stop estimating with time!
The US has had standing "temporary" policies of imprisonment or assassination without trial, torture, and mass invasion of privacy for almost 20 years now. There are limitations on the rights to equal protection, to assistance of counsel in criminal prosecutions, and to open access to court hearings, which are simply accepted as status quo.
Personally I would not argue that the US is not "free"... but if you want to talk about emergency limits of democracy encroaching upon that definition, IMO the War on Terror is a stronger argument.
As George Carlin put it, "Think of how stupid the average person is, and realize half of them are stupider than that."
I think here it's more accurate to say, "the business' impression of the end-user's perceived value".
Because a snappy user experience DOES have real value; in web we are very conscious that milliseconds cost viewers in load and response times. It's well documented that brand positivity is connected to load and response times.
But users don't know to tell you that until the performance gets REALLY bad. Consequently it's hard to get this value from a user survey, and hard to communicate internally as a value prop. Capabilities are much more business process friendly.
My projects are self contained again, even though they use global package stores, and my IDE can treat the package store dir as a part of the codebase for debugging. I love it.
And even if you're in a country (only really Germany AFAIK) where the worst use of metadata for advertising is legally tricky... WhatsApp is the very definition of the fox guarding the henhouse. Do you really trust one of the largest data harvesters andy advertising marketplaces in the world to guard your data? Their business model literally depends on violating that trust. Do you honestly think that's a safe long term bet?
You're already using an abstracted measure of time, by working with a derivative value of "developer estimated hours". You're already doing timeline projections on the average throughput of your "adjusted developer hours" unit. That's most of the value right there.
You can get even better results, with a little less cognitive load, by applying the research that people are much more consistent in estimating complexity than time (note that your method relies on consistency, not accuracy, to succeed). A quick imagination exercise validates this point for most of us: You bought a new IKEA sofa - how much time will it take to build? Honestly hard to do, and we're never accurate. But consider instead: how hard is it? Way easier to answer. And if you already know how long it takes you on average to finish other tasks of similar apparent difficulty...
Try using your exact same system, but ask people to estimate the task in terms of complexity. Use any scale you like, as long as the units have consistent value in your developers' minds (I like "cups of coffee", personally). Make your Dev team agree on the difficulty score for each Feature, to ensure that consistency.
Side benefit: Devs stop worrying about time and taking shortcuts (aka "technical debt") to meet their time estimate that you don't believe anyway. They're also a lot more likely to consider hidden risks and sources of extra complexity in the estimate.
Then you just track the actual throughput with a confidence interval, and use that to make timeline projections with a confidence interval based on that tracking.
TLDR: try asking Devs to estimate complexity rather than time, and use a moving average with confidence interval rather than the static 1.6 multiplier to make timeline projections. You'll find your projections more accurate and developers less stressed about it. You'll also have reinvented story points.
managing k8s yourself on bare metal is hard. Managed k8s on any provider is a real value.
Aside: There are other biases built into Italian singing that will trip up singers in spoken Italian, too. For example, Italian opera is largely written in a metric form where the phrase emphasis is ALWAYS on the last word. That teaches singers an instinct for odd sentence structure, or for putting a weird accent where it doesn't need to exist in speech.
You need to focus on the real problem at hand, and devise/adapt a correct solution in context. Systems and frameworks provide helpful tools and templates, but they all require contextual adaptation.
FWIW this is what I like about the foundations of Agile for project management. The manifesto points all direct you away from your tools and processes and towards the actual problem. eg "People over process," "working code over documentation," etc. Basically the people on the team should focus on working software, communicating with the customer, and adapting to change. Their processes, documentation, contracts, and plans should all be aligned to that solution, not the other way around.
And out of that... we got millions or scrum certificate weilding alcolytes who will tell you that if your project failed, it's because you didn't do their system religiously enough. God certainly has a sense of irony.
For singing, where my technique is a lot more advanced and it's more about memorization, I learn components in reverse chronological order, ie start with the last four bars, then the last 8 bars, then the last 12, etc. That way the piece is increasingly well memorized as I go along.
Side note: both duckduckgo and google gave me correct results for that specific search. Turns out "reservoir cats" is a movie and a simpsons episode.
But it's not a powerhouse CPU like this. A rock64 is no competition for a current generation Intel I5/7 AFAIK.
Hence the redesign around a client-server model, where MS could guarantee call quality a lot better, and which allowed for mobile to thrive.
None of which excuses the UI of course, or problems with the back end. Or lync, or any of the other problems. But it does give some context.