Why not use a challenge response system that communicates with low voltage current that passes over the skin. Then you can disable the weapon the moment direct physical contact is lost. Of course you'd need to ensure the current was low enough that it didn't cause your trigger finger to spasm...
And in firefox I've setup a smart folder that searches my live bookmarks for unread RSS entries, so even with a dozen or so feeds I still only need to look in one place. So I still can't see the point of twitter for aggregation.
For the record, those financial models were perfectly accurate.
You mean in that they assumed that because the risk of failure of one loan was X%, in a batch of N loans the risk of all N loans failing was X^N%? That doesn't sound like user error to me.
Our economy goes through boom and bust cycles, any student of history can tell you this. If your financial model does not demonstrate how boom and bust cycles occur, or at the very least include the risk of systemic failure, it is grossly negligent to apply it in the real world.
I think he meant something more like using a web service to handle the expected use case. Not a support environment where you are always dealing with the unexpected.
You wouldn't spiral in either direction unless there was some other force being applied. eg atmospheric drag or rockets. If you had a circular orbit and suddenly increased your velocity, you'd now be in a more elliptical orbit, not a spiral.
As a software developer I greatly appreciate the small number of times I've actually seen the software used by the end user. As this can give insight into how the process is used, what further automation can be done and what simple GUI improvements can be made to make the process more efficient. If such information is filtered out by the usual user > manager > analyst > developer chain of command, it makes my job that much harder.
Personally I think developers should eat their own cooking more. Get them out into various parts of the business from time to time so they can see exactly what is being done. Then they will be in a better position to offer advice on how they can improve on it.
ReactOS used to "draw heavily from wine". However at the time ReactOS started wine wasn't as well structured or functionally complete as it is today. This lead to ReactOS needing to heavily modify or rewrite huge sections of wine's codebase. This project is a restart of that code with a much cleaner separation now that both projects have matured somewhat.
Though there is still some data decoding happening in the blue ray player. HDMI doesn't carry an MPEG4 or h.264 encoded stream, it takes raw video frames. That said, I doubt the codec is any different between models.
Long term? You don't. But as the world moves to SIP or some other telephony solution that runs on the internet, some people in the world will be stuck for some time on a POTS exchange with a simple phone that can only dial numbers. So what if that exchange didn't have to use the normal international phone network but could use DNS to find a SIP server to route the call to directly over the internet?
From google's point of view it only has to be stable enough. They don't care that much if a node goes down or a single copy of a block of data becomes unavailable. What they care about is aggregate throughput for the entire cluster.
which requires, at least in the short term, getting its hands out of that pie, and allowing the economy to grow bereft of any regulations at the federal level
On that I must disagree. It is the removal of regulations that has lead us into this mess. I think the role of government should be to actively fight against any concentration of power in both the public and private sectors. So that all men may live free of slavery. The system we have now has far too much in common with the feudal system, in terms of concentration of power.
I dunno, I think the power of deleveraging is bigger than 10%. From memory, before this crisis Americans were spending in aggregate $1.3 or so for every $1 of actual income. The 0.30c came from home loans and credit cards, and all this extra lending stimulated the economy. Now that debt growth has reversed, there's at least 30% of the cashflow in the economy that no longer exists. This is why the govenment adding 2 trillion in bank reserves hasn't helped all that much. Nobody wants to borrow it and spend it. And no bank wants to take the risk you won't be able to pay.
Now if the government prints more money (or adds some electronic records somewhere to accomplish the same thing) they've already shown they will probably give it straight to the banks. And all the banks have done with the extra cash they've gotten so far is gamble it on various markets. The currency may be devalued when compared with other currencies. And that may help the government's debt problem since they're the ones printing the cash. But if the cash doesn't end up in the hands of consumers, actual prices for say coffee may still go down at the same time.
Which sounds like a poorly designed application to me. If your application / database depends on having upper case in certain fields, then they should be forced to be upper case by the application, not the capslock key.
Patenting the concept of putting a camera behind or infront of a screen is obvious and should not be allowed. Patenting a particular "how to" is reasonable.
Personally I'm rather fond of the nethood folders. They have a desktop.ini file to specify the class id and a target.lnk shortcut to the folder that should be displayed. Create your own shortcut to any folder and copy it in with a cmd prompt and you can point one of these folders anywhere you like.
I dunno, I was going to say something similar to the OP. Code spread over too many lines takes longer to understand as you have to trace through everything before you can piece it all together in your head. And before you can refactor it you have to understand all the different logic branches.
And why don't they teach these people something like morse code? Surely there's a better text encoding system you could use than playing 20 questions all the time.
That sounds fair-ish to me. At least for testing what needs to happen in production. Give the devs free reign to try something and make sure it works, but they must document what they've done and make sure it's repeatable.
Slashdot Mirror
And apparently he has already backed down.
But this law should never have been passed in the first place.
Why not use a challenge response system that communicates with low voltage current that passes over the skin. Then you can disable the weapon the moment direct physical contact is lost. Of course you'd need to ensure the current was low enough that it didn't cause your trigger finger to spasm...
And in firefox I've setup a smart folder that searches my live bookmarks for unread RSS entries, so even with a dozen or so feeds I still only need to look in one place. So I still can't see the point of twitter for aggregation.
But now there's an (almost) shipping product, there's a whole range of new topics to discuss. Like; will it blend, a step by step dis-assembly, etc.
For the record, those financial models were perfectly accurate.
You mean in that they assumed that because the risk of failure of one loan was X%, in a batch of N loans the risk of all N loans failing was X^N%? That doesn't sound like user error to me.
Our economy goes through boom and bust cycles, any student of history can tell you this. If your financial model does not demonstrate how boom and bust cycles occur, or at the very least include the risk of systemic failure, it is grossly negligent to apply it in the real world.
We don't have a magic password, but our call center support application can launch a browser window that bypasses the login process for any member.
I think he meant something more like using a web service to handle the expected use case. Not a support environment where you are always dealing with the unexpected.
You wouldn't spiral in either direction unless there was some other force being applied. eg atmospheric drag or rockets. If you had a circular orbit and suddenly increased your velocity, you'd now be in a more elliptical orbit, not a spiral.
As a software developer I greatly appreciate the small number of times I've actually seen the software used by the end user. As this can give insight into how the process is used, what further automation can be done and what simple GUI improvements can be made to make the process more efficient. If such information is filtered out by the usual user > manager > analyst > developer chain of command, it makes my job that much harder.
Personally I think developers should eat their own cooking more. Get them out into various parts of the business from time to time so they can see exactly what is being done. Then they will be in a better position to offer advice on how they can improve on it.
ReactOS used to "draw heavily from wine". However at the time ReactOS started wine wasn't as well structured or functionally complete as it is today. This lead to ReactOS needing to heavily modify or rewrite huge sections of wine's codebase. This project is a restart of that code with a much cleaner separation now that both projects have matured somewhat.
And how many embedded devices are there that support avi files but not mp4 / mkv?
Though there is still some data decoding happening in the blue ray player. HDMI doesn't carry an MPEG4 or h.264 encoded stream, it takes raw video frames. That said, I doubt the codec is any different between models.
Why would you want to keep the telephone number?
Long term? You don't. But as the world moves to SIP or some other telephony solution that runs on the internet, some people in the world will be stuck for some time on a POTS exchange with a simple phone that can only dial numbers. So what if that exchange didn't have to use the normal international phone network but could use DNS to find a SIP server to route the call to directly over the internet?
From google's point of view it only has to be stable enough. They don't care that much if a node goes down or a single copy of a block of data becomes unavailable. What they care about is aggregate throughput for the entire cluster.
which requires, at least in the short term, getting its hands out of that pie, and allowing the economy to grow bereft of any regulations at the federal level
On that I must disagree. It is the removal of regulations that has lead us into this mess. I think the role of government should be to actively fight against any concentration of power in both the public and private sectors. So that all men may live free of slavery. The system we have now has far too much in common with the feudal system, in terms of concentration of power.
I dunno, I think the power of deleveraging is bigger than 10%. From memory, before this crisis Americans were spending in aggregate $1.3 or so for every $1 of actual income. The 0.30c came from home loans and credit cards, and all this extra lending stimulated the economy. Now that debt growth has reversed, there's at least 30% of the cashflow in the economy that no longer exists. This is why the govenment adding 2 trillion in bank reserves hasn't helped all that much. Nobody wants to borrow it and spend it. And no bank wants to take the risk you won't be able to pay.
Now if the government prints more money (or adds some electronic records somewhere to accomplish the same thing) they've already shown they will probably give it straight to the banks. And all the banks have done with the extra cash they've gotten so far is gamble it on various markets. The currency may be devalued when compared with other currencies. And that may help the government's debt problem since they're the ones printing the cash. But if the cash doesn't end up in the hands of consumers, actual prices for say coffee may still go down at the same time.
And if you need the text out of a standard messagebox, use Ctrl+C. That's worked since win2k sp3 from memory but it should be better documented.
Which sounds like a poorly designed application to me. If your application / database depends on having upper case in certain fields, then they should be forced to be upper case by the application, not the capslock key.
Patenting the concept of putting a camera behind or infront of a screen is obvious and should not be allowed. Patenting a particular "how to" is reasonable.
Or an expensive bike lock you can open with the end of a BIC pen...
The current generation use a rotating circular polarisation, not just plain horz / vert like your sun glasses.
Personally I'm rather fond of the nethood folders. They have a desktop.ini file to specify the class id and a target.lnk shortcut to the folder that should be displayed. Create your own shortcut to any folder and copy it in with a cmd prompt and you can point one of these folders anywhere you like.
I dunno, I was going to say something similar to the OP. Code spread over too many lines takes longer to understand as you have to trace through everything before you can piece it all together in your head. And before you can refactor it you have to understand all the different logic branches.
And why don't they teach these people something like morse code? Surely there's a better text encoding system you could use than playing 20 questions all the time.
That sounds fair-ish to me. At least for testing what needs to happen in production. Give the devs free reign to try something and make sure it works, but they must document what they've done and make sure it's repeatable.