Please stop calling this an eruption. Kilauea has been erupting continuously since 1983. This is not a new eruption. This is a new rift, a new spot that lava comes out of the ground. There have been a number of these over the course of the ongoing eruption.
The eruption isn't over until the lava lake at the summit hardens and stops.
If you're pulsing, you can charge and release the charge on a capacitor. You only need a 300kw generator if you're (a) continuously sending or (b) pulsing at significantly greater energies.
Low volume of patients. High cost to invent the drug and pass the regulatory hurdles. And it has to subsidize all the drugs they researched that didn't work out. They need to make this money back over the lifetime of the patent or they go out of business.
A couple of researchers try to game that system and the company responds: Nope, prescribe the medicine the patient needs based on the medical evaluation only. We're going to make it cost exactly the same per patient regardless of the dosage you pick.
There are lots of facts here that I don't know. Do they need $150k per patient to break even? I don't know and neither do you. The part that I do know seems relatively reasonable.
'97 CS grad. All the exams were on paper. I don't recall being asked to write syntactically correct programs on paper. That's what the programming projects were for. The point of the paper exams was to check if I understood the *concepts*.
The difference is that Symantec doesn't have to care about anyone who isn't a paying customer. They just can't demand an NDA for the customer to see the code.
Obviously I was trying to be funny by connecting China's notorious reputation for intellectual property violations, the fact Microsoft developed the technology there and the apparent change in robocalling behaviors. Obviously you don't find it nearly as funny as I do.
The Chinese have already stolen this technology and are using it to robocall me.
I've had a couple of calls recently where I get the connect silence of a predictive dialer followed by a woman speaking with call center background noise. She gives her name and asks how I'm doing. The first time it happened it seemed off for reasons I can't quite articulate, so I asked: "Are you a robot or a person?" She responded "yes" and then launched in to a sales pitch. The next time I asked, "where can I direct your call?" She responded "that's good" and launched in to her pitch.
The White House could also turn the email servers off and lock them in the closet. Like DKIM this would have a negative impact on their function, but it would provide very solid guarantee on whether the received emails were legitimate.
SPF is okay in most email configurations. DMARC and DKIM are disaster areas which break common email scenarios like mailing lists.
Sure. After all, when people are struck by lightning which utterly shreds the then-current state carried in their nervous system, they wake up afterwards as entirely different people.
There's a point at which all but the greatest artisans maxes out the productivity they can achieve on their own. After that, your value only increases if you cause other peoples' utility to improve. That's not necessarily management. But it does require leading and mentoring other people.
Never mind that employers have basically made it impossible to continue working as a developer for them for a significant length of time, without going into management.
Never mind it because it isn't generally true.
I'm on a 12-month contract right now that ends in 2 months, and they cannot offer me a position or extend the contract because company policy requires them to put another person in this position after the contract ends. It's insane.
That's because they're gaming the tax system. They're treating you like a W2 employee but paying you like a 1099 contractor. Refusing to extend the contract lets them avoid getting convicted.
Until your company is down because one of those servers died.
That's what backups are for. In my case the "servers" are EC2 instances in AWS which can be returned to service from the daily snapshots in less than 5 minutes. Call it 30 minutes to allow for the time for a system administrator to receive an alert and respond.
On the other hand, re-engineering everything to eliminate all single points of failure would more than double the cost of the software. And if we wanted to really 100% eliminate all single points of failure, we'd have to move out of Amazon because they don't provide the tools to reach 100%. I know this from having designed and built a system that eliminated all single points of failure for a customer willing to pay the roughly $3M that it cost.
It is among my duties to advise the customer so that they can make an educated choice. It is not my job to usurp that choice.
Besides, not everybody needs 5-nines availability. Some systems are fine with 3-nines. Some achieve their mission with less than 2 nines. Paying for 5-nines when you didn't really need 2 nines would be a fool move.
I didn't become the lead devops guy by failing to automate repetitive work. I also didn't get here by trying to surf each new wave that comes to shore.
Docker and Kubernetes do some very interesting things. And they don't attempt to do a number of things that their predecessors eventually figured out were essential to reliable cost-effective operations. They will or they'll fade. When they do, I'll notice.
I hate to say it, but right now Docker is primarily a way for developers to stick their fingers in their ears and say "la la la security la la la." Require the same attention to security that the OS gets and suddenly Docker is massively more complex to work with than older techniques.
Conceptually I like docker, but unless I'm building something at a scale sufficient to justify the expense of doing it well, it doesn't meet my needs. And guess what? Most positions open to junior developers don't involve building something at high scale.
I'm doing what the customer wants done with his money. The customer made the call that downtime is acceptable while the cost of a highly resilient system is not.
"Wrong" is what the customer decides he does not want.
Slashdot Mirror
Please stop calling this an eruption. Kilauea has been erupting continuously since 1983. This is not a new eruption. This is a new rift, a new spot that lava comes out of the ground. There have been a number of these over the course of the ongoing eruption.
The eruption isn't over until the lava lake at the summit hardens and stops.
web.com is a Florida company. It should not be surrendering domain names without a proper order from a U.S. court.
Law enforcement doesn't shoot the car, they ram the car. Much safer, much more controlled.
If you're pulsing, you can charge and release the charge on a capacitor. You only need a 300kw generator if you're (a) continuously sending or (b) pulsing at significantly greater energies.
I don't know and neither do you.
I stand corrected.
Low volume of patients. High cost to invent the drug and pass the regulatory hurdles. And it has to subsidize all the drugs they researched that didn't work out. They need to make this money back over the lifetime of the patent or they go out of business.
A couple of researchers try to game that system and the company responds: Nope, prescribe the medicine the patient needs based on the medical evaluation only. We're going to make it cost exactly the same per patient regardless of the dosage you pick.
There are lots of facts here that I don't know. Do they need $150k per patient to break even? I don't know and neither do you. The part that I do know seems relatively reasonable.
'97 CS grad. All the exams were on paper. I don't recall being asked to write syntactically correct programs on paper. That's what the programming projects were for. The point of the paper exams was to check if I understood the *concepts*.
That makes the case for being allowed to test out of a class. Which should be allowed for any class that's not core to the curriculum.
Seems reasonable to me. Pay with cash or pay with your privacy. Facebook is a business not a charity. No one forces you to use them.
The difference is that Symantec doesn't have to care about anyone who isn't a paying customer. They just can't demand an NDA for the customer to see the code.
Obviously I was trying to be funny by connecting China's notorious reputation for intellectual property violations, the fact Microsoft developed the technology there and the apparent change in robocalling behaviors. Obviously you don't find it nearly as funny as I do.
The Chinese have already stolen this technology and are using it to robocall me.
I've had a couple of calls recently where I get the connect silence of a predictive dialer followed by a woman speaking with call center background noise. She gives her name and asks how I'm doing. The first time it happened it seemed off for reasons I can't quite articulate, so I asked: "Are you a robot or a person?" She responded "yes" and then launched in to a sales pitch. The next time I asked, "where can I direct your call?" She responded "that's good" and launched in to her pitch.
The White House could also turn the email servers off and lock them in the closet. Like DKIM this would have a negative impact on their function, but it would provide very solid guarantee on whether the received emails were legitimate.
SPF is okay in most email configurations. DMARC and DKIM are disaster areas which break common email scenarios like mailing lists.
The kernel is there to interface with the hardware. The Direct Rendering Manager interfaces with the graphics hardware.
How about letting me use the Direct Rendering Manager in X without disrupting my console text mode? Leave my text alone!
Sure. After all, when people are struck by lightning which utterly shreds the then-current state carried in their nervous system, they wake up afterwards as entirely different people.
This is a science fiction plot. It's been used more than once in a few fun story arcs.
I hope this wasn't a peer-reviewed paper. It would suck if we're sunk so low as to publish science fiction plot studies as peer-reviewed science.
There's a point at which all but the greatest artisans maxes out the productivity they can achieve on their own. After that, your value only increases if you cause other peoples' utility to improve. That's not necessarily management. But it does require leading and mentoring other people.
Never mind that employers have basically made it impossible to continue working as a developer for them for a significant length of time, without going into management.
Never mind it because it isn't generally true.
I'm on a 12-month contract right now that ends in 2 months, and they cannot offer me a position or extend the contract because company policy requires them to put another person in this position after the contract ends. It's insane.
That's because they're gaming the tax system. They're treating you like a W2 employee but paying you like a 1099 contractor. Refusing to extend the contract lets them avoid getting convicted.
The last restore took 23 minutes from notification to return to operation. And there's nothing like a real-life recovery as a successful "test."
Per the customer, an annualized unplanned downtime of 175 hours is acceptable.
Job-hopping is not a good plan. I've turned down more than one applicant because of an unstable job history. Trust me, we notice.
Plan to stay at least 2 years unless the job completely sucks. A bunch of 6 and 12 month jobs on your resume is a huge red flag.
Until your company is down because one of those servers died.
That's what backups are for. In my case the "servers" are EC2 instances in AWS which can be returned to service from the daily snapshots in less than 5 minutes. Call it 30 minutes to allow for the time for a system administrator to receive an alert and respond.
On the other hand, re-engineering everything to eliminate all single points of failure would more than double the cost of the software. And if we wanted to really 100% eliminate all single points of failure, we'd have to move out of Amazon because they don't provide the tools to reach 100%. I know this from having designed and built a system that eliminated all single points of failure for a customer willing to pay the roughly $3M that it cost.
It is among my duties to advise the customer so that they can make an educated choice. It is not my job to usurp that choice.
Besides, not everybody needs 5-nines availability. Some systems are fine with 3-nines. Some achieve their mission with less than 2 nines. Paying for 5-nines when you didn't really need 2 nines would be a fool move.
I didn't become the lead devops guy by failing to automate repetitive work. I also didn't get here by trying to surf each new wave that comes to shore.
Docker and Kubernetes do some very interesting things. And they don't attempt to do a number of things that their predecessors eventually figured out were essential to reliable cost-effective operations. They will or they'll fade. When they do, I'll notice.
I hate to say it, but right now Docker is primarily a way for developers to stick their fingers in their ears and say "la la la security la la la." Require the same attention to security that the OS gets and suddenly Docker is massively more complex to work with than older techniques.
Conceptually I like docker, but unless I'm building something at a scale sufficient to justify the expense of doing it well, it doesn't meet my needs. And guess what? Most positions open to junior developers don't involve building something at high scale.
I'm doing what the customer wants done with his money. The customer made the call that downtime is acceptable while the cost of a highly resilient system is not.
"Wrong" is what the customer decides he does not want.