I have a brilliant answer to your question. But it seems like you want it answered for a big shiny price of "free". I'll keep it to myself. Oh, and if you are thinking of having a contest and hope to get my idea without actually paying for it (and no, having a contest is not it), you can forget about it. I won't submit to any such contest. If you want data analytics ideas start paying people who spend time of their lives learning how to do data analytics.
Given that the workforce is shrinking because birth rates didn't match the retiring population numbers, any profession which keeps its numbers is increasing in percentage of the workforce.
By the one of the few newspapers trying to charge for printed content on the Internet: free is bad for you. No self-serving there. I am appalled (appalled!) that there is gambling going on in here.
One is gambling ones reputation when making a public prediction. But the estimating a value of one public statement (correct or incorrect) is unenumerated. Money is a token for enumerating exchange. Currency doesn't have to exist in the form issued by a government entity. Stackexchange, for example, is pretty good at enumerating reputation gains and losses (and has methods for staking ones reputation gains on answers to certain questions). It's hardly surprising that enumerated exchange of knowledge is more precise than unenumerated one.
You are either simulating instructions (binary translation in VMWare terms) or you are letting the processor run them directly. If you do binary translation, all performance is abysmally slow. So you essentially set it up to pass through instructions to the CPU. If you do that and the number of CPU cores you use up is higher than the number of cores you actually have, then performance slows to virtually nothing (even slower than binary translation). On Intel with 4 cores and hyperthreading you'll get to that point even with 4 VMs (you do need VT-x enabled in BIOS). On AMD (you do need VT-d enabled in BIOS) you can run 5 VM without binary translation and they perform. So the 8 cores are 8 actual CPU cores.
BTW, the cores 2,4,6,8 ship parked. You need to go through a bit of initial effort to unpark them. So they are really NOT just additional features added to CPUs 1,3,5,7. They independent. Show me how to run 5 VM's independently at the same time on 4 hyperthreaded core processor. I tried it. It freezes even if you have plenty of memory left. Because it has to start context swapping between multiple VMs's. Which essentially means cache is invalidated. Not sure if hyperthreading ever happens either. On AMD, 5 VMs and 1 host don't even slow down. There is no difference in the performance of each VM if the others are turned off.
They do have 8 CPU cores. You can run 8 OS's (1 host and 7 guest VMs) on it. Yes, I tried it. It works on AMD. It doesn't on Intel (essentially freezes on Intel).
Yes, you get the Intel machine for high performance applications and AMD for running lots of VMs. FPU is not needed for basically anything but computational stuff. If you want to run a few systems and compile in a few different environments (linux/windows/32 bits/64 bits... that's already a combo of 4), you get AMD and lots of memory.
I run at least 5 VMs on it. And they all run all the time (in addition to the host OS). It also took some initial effort to unpark every other core. Which means cores 2,4,6,8 can be parked independently of their cousins. AMD chips are better for running VMs, while Intel chips are better at running games. I couldn't run 5 VM's on Intel 5 (4 cores with hyperthreading). The actual CPU count is 8 on the AMD chip. You don't need an FPU to run basic operating system threads themselves. It also has more symmetric caching. Whereas Intel's caching is clearly geared at increasing the speed up of each running core.
What if the manufacturer deems vehicle electronics to be its trade secret and explicitly prohibits anyone from disassembling it without prior written authorization? It doesn't say whose authorization. The provision should only cover vehicles in motion or in operation. Or manufacturers' lawyers will find the language to lock everyone but the licensed parties out of the process. Congress has the power to establish IP regimes. It's not limited to trade marks, patents and copyrights. The mode of the regime can be of Congress' choosing. Making the working this general would most likely survive any court challenges.
Any vehicle "data hacking"? Or a vehicle in motion? Otherwise, accessing data of a car's computer while the car is stationary would be a crime. So this would have made the VW investigators criminals. It would also make anyone creating a 3rd device reading on-board computer data illegal without a license from the manufacturer. If you can't introspect a car without putting in jeopardy anyone's safety, then this is just another DMCA.
K&R leaves a lot to imagination when it comes to describing C. Even if you are living back in the 90's, you won't be proficient in C until you've read "C: A Reference Manual" by Harrison & Steele.
Does it help? The total amplitude of the ovens is so much higher than anything any wifi antenna should ever put out (without frying anyone standing next to it) that what the oven leaks into its surrounding band should be enough to interfere with most WiFi channels. http://mars.nasa.gov/MPF/rover...
So he is full of it. DevOps is not about ops engaging with devs. It's about making all devs part of ops. It's a model which existed in commercial banks and other places which could afford to overpay (a lot) to have people do work a few notches below the pay grade they are paid. But it's high stress and snail-pace progress. It reduces specialization which, by definition, makes experience less valuable. It puts all of the testing burden on the developers and removes testing specialists. In the most extreme cases, it flattens the most experienced developers and newly minted college interns into doing the same job. The result is that the quality of the product is always determined by what the least skilled members of the team can handle. Oh, and because everyone is resentful and knows that they are overqualified, it creates a frat-house-like environment. Everyone end up overworked and under accomplished. But because it's used in the cloud management now (an industry growing quickly so it has as much money to burn as the banks), it creates the illusion of being successful. It's not.
The cloud started before there was dev ops. And it would continue and succeed without dev ops. It exists because all development is network development (to at least some degree) because CPUs can't be made much more powerful, they can only be networked on the chip (aka multi-core CPUs, GPU). And if there is no distinction between pooling multi-computer resources and pooling multi-core resources, then scaling is accomplished by pooling a lot of them in near-real-time batch processing (aka pipeline). Which means the state of technology makes the cloud computing model make more sense than stand-alone units computing model. The state of technology is what drives the business incentive here. And the business incentive is what creates the illusion that the fulfillment model of the business incentive is the right one. Even if it's not organization model. Poorly chosen organization model in the environment of over-funding will not fail until the market place becomes more efficient and consolidates. And at that time, all the DevOps shops will be unable to support their costs and won't understand why everyone is switching to well-engineered (through full SDLC) products. They'll be saying it's not in vogue anymore. While the reality is that DevOps is just an inefficient organizational model to develop cloud services.
Not everyone enjoys slamming, you know. Sure the chicks are to impress, but after a while you feel like "what's the point?"... Wait, you meant $100-burger as a luxury, didn't you? Um... I gotta go.
It's the influx of people combined with the 2% excise tax imposed on sellers that's keeping people from selling. There is also a lot of ordinances making it more difficult to rent. Basically, Seattle still has laws formed during the mind set of "we have to keep people from leaving without leaving some money behind" which was formed when it was slowly declining. The end result is that while apartment owners have more difficult time renting, there is an increase demand for rental space. And that means only really Big Money can create rental space (by buying out and building up).
"Diverse"? "Historically"? C'mon. Seattle has the highest ratio of Caucasians of any metropolitan area and it's been that way for a very, very long time. It's main function before the tech boom was as a port to Asia and Alaska. Oh, and the new constructions are actually quite beautiful. But I guess you can't argue about taste (even in architecture). Oh, and if there is any low brow behavior, it's more likely from the port workers than from Amazon employees (who are far too busy to care about drag queens).
Most of Eastside (even more so than WA) has very anti-competitive housing laws. It's all geared against keeping renters out and benefiting orthodoxy. This discourages building, but it's also the reason why Greater Seattle didn't participate in the housing crash of 2008. But, as with any market place obstacle, market place treats obstacles the way rivers treat boulders... a large obstacle can slow the flow for a while, but it's just a build up which will eventually burst through. Builders will find loop holes. The renting prices are already in a mini crash.
Well, DevOps is the only way to make any use of millennials. It's geared towards people who cannot work on the same task for 3 days, let alone 3 months.
I know that this is a true-Scotsman type of argument, but this only proves does not necessarily disprove the hypothetical man-month argument is wrong. It proves that either hypothetical man-month argument is wrong or DevOps are not development projects (this is the more likely scenario). While it may seem like problems are fixed faster in DevOps vs SDLC, the reality is that it forces all users to be perpetual alpha testers (that's right... not beta testers... alpha). DevOps is why a cell phone bought 3 years ago cannot function anymore unless you upgrade it and slowly cede more and more control over your private info to be data mined. It makes devices less and less programmed and more and more terminals to data centers. And if the devices are not programmed, then the process which maintains them is not a development process. The most successful end-user operating system of all time is Windows XP. Except it's not. All XP machines are perpetually upgraded. It's why MS has decided that Win 10 will be last update of the operating system. After that there will only be upgrades... perpetual alpha. The truth is that it only worked because it had a solid foundation in the NT kernel. No amount of DevOps scale out could have created that.
The mythical man month was a declaration that software which can continue to work without updates for 20 years cannot be made faster by throwing more people to plaster band-aids on it as it bleeds faster. DevOps, as a permanent fixture, is only a few years old and it only appeals to millennials who think that multitasking (as opposed to deep thinking) is a merit. The fundamental structural problems that find their way into the system and can one day bring it down will necessarily be missed. Band-aids only work for so long.
At least, they have a sense of humor about it. "But no credit card numbers were stolen"? Who would need that after they have your SSN, full name, address, birthday, driver's license and PASSPORT NUMBER? That's enough to have any credit card you want. Wait, they don't have a sense of humor, do they? They are not kidding, are they? They really do think this cloud has a silver lining? Oh, what the hell. If the Secretary of State can send emails through an unsecured server, and the IRS has a 6-month's data retention policy and can get away with claiming 6 simultaneous employees' harddrives crashed right after receiving subpoenas, maybe Experian does get to get away with "but no credit card numbers were stolen" bull shit.
Slashdot Mirror
you are mistaken. i am not a lawyer.
I have a brilliant answer to your question. But it seems like you want it answered for a big shiny price of "free". I'll keep it to myself. Oh, and if you are thinking of having a contest and hope to get my idea without actually paying for it (and no, having a contest is not it), you can forget about it. I won't submit to any such contest. If you want data analytics ideas start paying people who spend time of their lives learning how to do data analytics.
So your friend worked for lottery security and he told you the numbers and that's how you won the lottery...
Ummm... what? I did win the lottery. And my friend did tell me the numbers. But he told me BEFORE the numbers were picked.
Yeah, that's what we are saying
So why am I on trial.
Because your friend worked for lottery security and he told you the numbers and that's how you won the lottery...
Oh, boy.
Given that the workforce is shrinking because birth rates didn't match the retiring population numbers, any profession which keeps its numbers is increasing in percentage of the workforce.
By the one of the few newspapers trying to charge for printed content on the Internet: free is bad for you. No self-serving there. I am appalled (appalled!) that there is gambling going on in here.
One is gambling ones reputation when making a public prediction. But the estimating a value of one public statement (correct or incorrect) is unenumerated. Money is a token for enumerating exchange. Currency doesn't have to exist in the form issued by a government entity. Stackexchange, for example, is pretty good at enumerating reputation gains and losses (and has methods for staking ones reputation gains on answers to certain questions). It's hardly surprising that enumerated exchange of knowledge is more precise than unenumerated one.
Well, and you may have cancer. Let's treat it just in case.
You are either simulating instructions (binary translation in VMWare terms) or you are letting the processor run them directly. If you do binary translation, all performance is abysmally slow. So you essentially set it up to pass through instructions to the CPU. If you do that and the number of CPU cores you use up is higher than the number of cores you actually have, then performance slows to virtually nothing (even slower than binary translation). On Intel with 4 cores and hyperthreading you'll get to that point even with 4 VMs (you do need VT-x enabled in BIOS). On AMD (you do need VT-d enabled in BIOS) you can run 5 VM without binary translation and they perform. So the 8 cores are 8 actual CPU cores.
BTW, the cores 2,4,6,8 ship parked. You need to go through a bit of initial effort to unpark them. So they are really NOT just additional features added to CPUs 1,3,5,7. They independent. Show me how to run 5 VM's independently at the same time on 4 hyperthreaded core processor. I tried it. It freezes even if you have plenty of memory left. Because it has to start context swapping between multiple VMs's. Which essentially means cache is invalidated. Not sure if hyperthreading ever happens either. On AMD, 5 VMs and 1 host don't even slow down. There is no difference in the performance of each VM if the others are turned off.
They do have 8 CPU cores. You can run 8 OS's (1 host and 7 guest VMs) on it. Yes, I tried it. It works on AMD. It doesn't on Intel (essentially freezes on Intel).
Yes, you get the Intel machine for high performance applications and AMD for running lots of VMs. FPU is not needed for basically anything but computational stuff. If you want to run a few systems and compile in a few different environments (linux/windows/32 bits/64 bits... that's already a combo of 4), you get AMD and lots of memory.
I run at least 5 VMs on it. And they all run all the time (in addition to the host OS). It also took some initial effort to unpark every other core. Which means cores 2,4,6,8 can be parked independently of their cousins. AMD chips are better for running VMs, while Intel chips are better at running games. I couldn't run 5 VM's on Intel 5 (4 cores with hyperthreading). The actual CPU count is 8 on the AMD chip. You don't need an FPU to run basic operating system threads themselves. It also has more symmetric caching. Whereas Intel's caching is clearly geared at increasing the speed up of each running core.
What if the manufacturer deems vehicle electronics to be its trade secret and explicitly prohibits anyone from disassembling it without prior written authorization? It doesn't say whose authorization. The provision should only cover vehicles in motion or in operation. Or manufacturers' lawyers will find the language to lock everyone but the licensed parties out of the process. Congress has the power to establish IP regimes. It's not limited to trade marks, patents and copyrights. The mode of the regime can be of Congress' choosing. Making the working this general would most likely survive any court challenges.
Any vehicle "data hacking"? Or a vehicle in motion? Otherwise, accessing data of a car's computer while the car is stationary would be a crime. So this would have made the VW investigators criminals. It would also make anyone creating a 3rd device reading on-board computer data illegal without a license from the manufacturer. If you can't introspect a car without putting in jeopardy anyone's safety, then this is just another DMCA.
K&R leaves a lot to imagination when it comes to describing C. Even if you are living back in the 90's, you won't be proficient in C until you've read "C: A Reference Manual" by Harrison & Steele.
Does it help? The total amplitude of the ovens is so much higher than anything any wifi antenna should ever put out (without frying anyone standing next to it) that what the oven leaks into its surrounding band should be enough to interfere with most WiFi channels. http://mars.nasa.gov/MPF/rover...
So he is full of it. DevOps is not about ops engaging with devs. It's about making all devs part of ops. It's a model which existed in commercial banks and other places which could afford to overpay (a lot) to have people do work a few notches below the pay grade they are paid. But it's high stress and snail-pace progress. It reduces specialization which, by definition, makes experience less valuable. It puts all of the testing burden on the developers and removes testing specialists. In the most extreme cases, it flattens the most experienced developers and newly minted college interns into doing the same job. The result is that the quality of the product is always determined by what the least skilled members of the team can handle. Oh, and because everyone is resentful and knows that they are overqualified, it creates a frat-house-like environment. Everyone end up overworked and under accomplished. But because it's used in the cloud management now (an industry growing quickly so it has as much money to burn as the banks), it creates the illusion of being successful. It's not.
The cloud started before there was dev ops. And it would continue and succeed without dev ops. It exists because all development is network development (to at least some degree) because CPUs can't be made much more powerful, they can only be networked on the chip (aka multi-core CPUs, GPU). And if there is no distinction between pooling multi-computer resources and pooling multi-core resources, then scaling is accomplished by pooling a lot of them in near-real-time batch processing (aka pipeline). Which means the state of technology makes the cloud computing model make more sense than stand-alone units computing model. The state of technology is what drives the business incentive here. And the business incentive is what creates the illusion that the fulfillment model of the business incentive is the right one. Even if it's not organization model. Poorly chosen organization model in the environment of over-funding will not fail until the market place becomes more efficient and consolidates. And at that time, all the DevOps shops will be unable to support their costs and won't understand why everyone is switching to well-engineered (through full SDLC) products. They'll be saying it's not in vogue anymore. While the reality is that DevOps is just an inefficient organizational model to develop cloud services.
You can just turn your microwave oven. It'll do a pretty good job of interfering with WiFI frequency (which is in the microwave band)
You have obviously never eaten a $100 hamburger.
Not everyone enjoys slamming, you know. Sure the chicks are to impress, but after a while you feel like "what's the point?"... Wait, you meant $100-burger as a luxury, didn't you? Um... I gotta go.
It's the influx of people combined with the 2% excise tax imposed on sellers that's keeping people from selling. There is also a lot of ordinances making it more difficult to rent. Basically, Seattle still has laws formed during the mind set of "we have to keep people from leaving without leaving some money behind" which was formed when it was slowly declining. The end result is that while apartment owners have more difficult time renting, there is an increase demand for rental space. And that means only really Big Money can create rental space (by buying out and building up).
"Diverse"? "Historically"? C'mon. Seattle has the highest ratio of Caucasians of any metropolitan area and it's been that way for a very, very long time. It's main function before the tech boom was as a port to Asia and Alaska. Oh, and the new constructions are actually quite beautiful. But I guess you can't argue about taste (even in architecture). Oh, and if there is any low brow behavior, it's more likely from the port workers than from Amazon employees (who are far too busy to care about drag queens).
Most of Eastside (even more so than WA) has very anti-competitive housing laws. It's all geared against keeping renters out and benefiting orthodoxy. This discourages building, but it's also the reason why Greater Seattle didn't participate in the housing crash of 2008. But, as with any market place obstacle, market place treats obstacles the way rivers treat boulders... a large obstacle can slow the flow for a while, but it's just a build up which will eventually burst through. Builders will find loop holes. The renting prices are already in a mini crash.
Well, DevOps is the only way to make any use of millennials. It's geared towards people who cannot work on the same task for 3 days, let alone 3 months.
I know that this is a true-Scotsman type of argument, but this only proves does not necessarily disprove the hypothetical man-month argument is wrong. It proves that either hypothetical man-month argument is wrong or DevOps are not development projects (this is the more likely scenario). While it may seem like problems are fixed faster in DevOps vs SDLC, the reality is that it forces all users to be perpetual alpha testers (that's right... not beta testers... alpha). DevOps is why a cell phone bought 3 years ago cannot function anymore unless you upgrade it and slowly cede more and more control over your private info to be data mined. It makes devices less and less programmed and more and more terminals to data centers. And if the devices are not programmed, then the process which maintains them is not a development process. The most successful end-user operating system of all time is Windows XP. Except it's not. All XP machines are perpetually upgraded. It's why MS has decided that Win 10 will be last update of the operating system. After that there will only be upgrades... perpetual alpha. The truth is that it only worked because it had a solid foundation in the NT kernel. No amount of DevOps scale out could have created that.
The mythical man month was a declaration that software which can continue to work without updates for 20 years cannot be made faster by throwing more people to plaster band-aids on it as it bleeds faster. DevOps, as a permanent fixture, is only a few years old and it only appeals to millennials who think that multitasking (as opposed to deep thinking) is a merit. The fundamental structural problems that find their way into the system and can one day bring it down will necessarily be missed. Band-aids only work for so long.
At least, they have a sense of humor about it. "But no credit card numbers were stolen"? Who would need that after they have your SSN, full name, address, birthday, driver's license and PASSPORT NUMBER? That's enough to have any credit card you want. Wait, they don't have a sense of humor, do they? They are not kidding, are they? They really do think this cloud has a silver lining? Oh, what the hell. If the Secretary of State can send emails through an unsecured server, and the IRS has a 6-month's data retention policy and can get away with claiming 6 simultaneous employees' harddrives crashed right after receiving subpoenas, maybe Experian does get to get away with "but no credit card numbers were stolen" bull shit.