Just look at the gold price over the past 100 years, even the last 10-15 years have seen an modest increase. It will only go up & it is highly unlikely that it won't ever be perceived as the asset compared to other precious metals.
From my experience it doesn't define it. However its becoming the standard for documenting your REST based HTTP API's and it's a focal point of the API itself to developers/stakeholders.
The audio processing loop wouldn't benefit from using the GPU because we can already hit above audible sample rates. Beefy GPU's are usually noisy too so you don't want one in your rig.
American healthcare is run by the private sector with pretty much zero accountability compared to say, the UK, where the NHS is for the most part, a public organisation with open books.
As a tester myself, who's worked in multiple consultancy roles... It depends on vendor obviously but also on time and money. Do you have a budget and a timescale?
Depending on how fundamental the changes are, I agree. However, usually when someone says that to me, its a huge smell that the unit tests are bloated and cover too much.
The major thing for me is proper search and filtering tools. Jira and TFS seem to get this right with JQL and Queries respectively, for most non-technical people however, they seem to be quite daunting.
I think the other main thing that could be improved is integration with other tracking software.
I work in testing. The main thing I see is projects using more than one project or defect management tool. I feel is an area that could be seriously disrupted.
For example... One project I worked, we had the developers (external company) using JIRA, whilst we used Smartbear ALM.
So I ended up writing something that used both the JIRA and ALM API's to save me updating two systems. Imagine if this functionality was out of the box?
Leaving it for ten minutes/waiting for the flour to hydrate then mixing again can help out when the temperature is off.