So if you read what I wrote, I did not suggest returning to paying for cable television. I suggested making a good faith effort to pay for the specific content that he wanted to watch.
This is exactly what I do personally, by the way. I cut the cord a while ago, but I really like watching live baseball. So I pay for a subscription to MLB.tv and watch it on my Roku box. There are a few other shows that my family enjoys but aren't on network TV, so I pay for those specific shows, as well. But that's it. I'm saving $1,164 per year by not having cable TV, so I figure it's only fair to kick some of that back for the content that I actually want to watch.
And to tell the truth, there have been a few instances where a particular episode or movie was not offered for sale, so I did wind up torrenting it. But this is after having hunted, with credit card in hand, for what I wanted to watch. I was ready to pay for it, but wasn't given that option.
I agree with you that a-la-carte should be by show, not by channel, but I can't agree with your logic of torrenting everything. If you want entertainment, then you really ought to pay the creator of that entertainment. It wasn't free to produce, and you get value out of it, so you should pay. If you didn't get any value, you wouldn't waste time watching it.
Might I suggest a compromise? Pull out your credit card and make a good faith effort to pay for what you watch. If that option isn't available, see if there is a good, free substitute. If neither of those options is available, then at least you tried to do the right thing. Torrent away.
My company will only book the cheapest fare (X or lower),
Get a doctor to certify that you need X inches of legroom when you fly or [bad medical outcome] will happen to you. Then, go to HR and say, "Need reasonable accommodation. Doctor's orders." My guess is that you and your knees will be pleasantly surprised.
Don't wanna be strangled? Don't have a neck. Don't want your car stolen? Don't own a car. Stealing is wrong no matter the context.
So you're right, I don't want my car stolen. And while I understand the point that you are making, I absolutely do take precautions to mitigate my risk of auto theft, and I bet you do too. I don't park my car on the street in certain parts of town, for instance. Neither do I leave my keys inside nor leave the doors unlocked nor leave my bike racks on it. Do you do the same, or similar? I bet you do, and if not, then you should.
In an ideal world, such precautions would be ludicrous. Why should I have to pay attention to where I park my car or whether or not I lock the doors? Stealing is wrong, goddamnit, and nobody should do it! But, it seems people do steal, even though it is wrong.
We don't live in an ideal world, so we have to deal with the world where we do live. And that means taking some steps to manage our risk of suffering criminal acts against us. The victim is not at fault, of course, but being not-at-fault doesn't take away the pain of having been victimized.
If you don't enjoy dealing with Retentions muppets, it's much easier to terminate a service in writing (or in the case of telephone service, by porting your number to a new provider). Check your terms and conditions for the official way to terminate, and you'll find the address there. Write them a letter and be done with it. There's no one to argue with you, that way.
Most ISPs have an "email only" product. They don't advertise it, but if you call, you'll probably find that for like $25/yr, they'll keep your email service alive for you.
So, to paraphrase Prof. Norm Matloff, is it stupid to buy expensive TI-8x milk when the R cow is free?
I don't know much about cows or milk, but if we could figure out a way to teach our kids R instead of how to use a TI-8x that they'll never touch again after graduation, we would be doing them a huge service.
Unless you're targeting an embedded system with resource constraints, I see no reason not to implement it similar to the above.
It's straightforward. You're unlikely to introduce any bit-twiddling bugs. It wouldn't take more than a few minutes to write and debug. And, most importantly, it's readable for people who aren't accustomed to bitwise operations.
Because when someone asks a question, they rarely want to know what they asked.
This is absolutely true.
For today's interview, the role had no J2EE component to it at all. But the resume said "expert", so I have to ask the question. I need to know if we're being lied to.
Just to be clear, I don't think that I have seen an actual EJB in probably a decade. But when someone puts "expert" on his or her resume, then I need to ask about it.
There have been questions of my ability to do what is on my resume that are legit.
I do a lot of technical interviewing, and that is the whole point of a technical interview, to verify that you actually do possess the skills that you have claimed to possess.
It's not because you're black. It's because you're interviewing. I could tell so many stories of wild resume claims, you'd laugh.
Here's one from today, for an interviewee who was an "expert in J2EE".
Q: What are some different types of EJBs and how do they differ from one another? A: [uncomfortable silence]. Q: Sorry, let's back up a bit. Tell me about your role in your last project that used J2EE. A: Uhh, I think I made a JSP once in college before I left to go work at a startup.
As you might expect, his resume got filed away in the recycling bin.
I used to use firefox, but when they fired an executive for an ancient political contribution, I decided I couldn't use a browser made by that company. So now I use Chrome.
For the record, I don't even agree with the executive's cause that he contributed to. But firing an executive for making a political contribution is dangerous ground, so I can't support that.
You realize that there's more difference between your average man and your average woman than between your average NFL linebacker and your average man, right? (seriously, compare the stats some time - height, average bench strength, etc).
This is almost certainly wrong, by the way.
Have you ever watched draft combine footage? Those linebackers do 20 or even 30 reps of 225 lbs like it's nothing. Some linemen have a one rep max of 500 or 600 lbs. 400 lbs is common.
I don't know what the average man and woman can bench, but NFL linemen are insanely strong. One could easily pick me up and throw me across the room like a ragdoll. I could not do the same with my wife. I could pick her up and put her over my shoulder or something, but there is just no comparison to an NFL lineman.
I understand well that men are stronger than women on average. No dispute there. I just think that a lot of people don't realize just how insanely strong NFL linemen are. This is a huge part of why football is so dangerous.
Oh, a human definitely needs to be there for maintenance. You can't automate fixing up a screwup in the automation.
I just see no reason why maintenance windows have to be done at 1am. In today's world of redundancy and failover, there is just no reason for it. Every upgrade my team has done for as long as I can remember has been at 10am local time because we don't allow downtimes anyway. Why work at 1am?
Go around a data center and look at all the Oracle database instances that are single-instance...that's because Oracle rapes you on licensing
Then stop using Oracle if you can't afford RAC/GoldenGate/TAF/whatever. Use what you can afford in order to architect a proper redundant system. Running a database on a single instance is malpractice in 2014.
Even our network upgrades we do in the middle of the workday. After all testing is done, we just take a whole datacenter down and upgrade it. Once it's back online, we do the next datacenter until it's all done.
There's really no reason in 2014 to do 1am maintenance.
You should always have a competent tech on hand for maintenance tasks.
I agree with this, but who does maintenance at 1am anymore? What's the point in it? Users are worldwide, and 1am in the US prime business hours in Asia, so why bother patching/upgrading in the middle of the night?
I haven't done a late-night maintenance in at least a decade. It's all about rolling upgrades. Any problems? Rollback. Need to upgrade infrastructure? Take the entire datacenter offline and serve from your other datacenters. Every single upgrade I've done for as long as I can remember has been at 10am, which is the earliest I can get my lazy-ass junior devs to stumble into the office.
Only the most motivated people are going to go through all the hassle and work that it takes to actually get here, so of course they are more likely to be successful once they do.
Jewish immigrants after WWII came here because they had nowhere else to go, not because they wanted the hassle of moving to a country on the other side of the world where they didn't speak the language, didn't know anybody, etc. Their homes had been taken when they were transferred to death camps, and very few countries were willing to take them in. They seem to have turned out OK, though.
And less cooking liquid vs. non-pressurized applications since very little steam is lost once the cooker as achieved pressure. Once the desired pressure is reached, you turn the burner onto its lowest setting while the food cooks.
There are a few other things that add to pressure cooking's efficiency. This is from a person who uses a pressure cooker (me), not an expert in heat transfer nor any other discipline of physics.
1. Most pressure cooker applications other than soup are steaming applications, and since the pressure cooker traps the steam in, you don't use nearly as much liquid as you would in traditional cooking. Less liquid = less energy to heat it up. 2. Less loss of heat through the top. After a pressure cooker reaches the desired pressure, you actually turn the burner down to its lowest setting (or whatever the lowest setting is on your stove to maintain pressure--on my stove, it's the lowest).
That's all I can think of for now, but I will say that a pressure cooker is a neat cooking tool. Especially if you live in a hot climate, like I do. Most of my summer cooking is on the grill, naturally, but I use the pressure cooker a bit, too, and it doesn't heat my house up too badly.
However, ever since the Boston marathon bombing manhunt, the authorities don't like people buying pressure cookers.
That's just not true. I bought my pressure cooker after the Boston Marathon bombings, and nobody gave me a second look. Anyway, modern pressure cookers have multiple safety mechanisms so they don't go boom like your grandma's pressure cooker did.
Slashdot Mirror
So if you read what I wrote, I did not suggest returning to paying for cable television. I suggested making a good faith effort to pay for the specific content that he wanted to watch.
This is exactly what I do personally, by the way. I cut the cord a while ago, but I really like watching live baseball. So I pay for a subscription to MLB.tv and watch it on my Roku box. There are a few other shows that my family enjoys but aren't on network TV, so I pay for those specific shows, as well. But that's it. I'm saving $1,164 per year by not having cable TV, so I figure it's only fair to kick some of that back for the content that I actually want to watch.
And to tell the truth, there have been a few instances where a particular episode or movie was not offered for sale, so I did wind up torrenting it. But this is after having hunted, with credit card in hand, for what I wanted to watch. I was ready to pay for it, but wasn't given that option.
I agree with you that a-la-carte should be by show, not by channel, but I can't agree with your logic of torrenting everything. If you want entertainment, then you really ought to pay the creator of that entertainment. It wasn't free to produce, and you get value out of it, so you should pay. If you didn't get any value, you wouldn't waste time watching it.
Might I suggest a compromise? Pull out your credit card and make a good faith effort to pay for what you watch. If that option isn't available, see if there is a good, free substitute. If neither of those options is available, then at least you tried to do the right thing. Torrent away.
My company will only book the cheapest fare (X or lower),
Get a doctor to certify that you need X inches of legroom when you fly or [bad medical outcome] will happen to you. Then, go to HR and say, "Need reasonable accommodation. Doctor's orders." My guess is that you and your knees will be pleasantly surprised.
Do you also bitch about being paid more because you are tall? Or is it just when it starts costing you?
Don't wanna be strangled? Don't have a neck. Don't want your car stolen? Don't own a car. Stealing is wrong no matter the context.
So you're right, I don't want my car stolen. And while I understand the point that you are making, I absolutely do take precautions to mitigate my risk of auto theft, and I bet you do too. I don't park my car on the street in certain parts of town, for instance. Neither do I leave my keys inside nor leave the doors unlocked nor leave my bike racks on it. Do you do the same, or similar? I bet you do, and if not, then you should.
In an ideal world, such precautions would be ludicrous. Why should I have to pay attention to where I park my car or whether or not I lock the doors? Stealing is wrong, goddamnit, and nobody should do it! But, it seems people do steal, even though it is wrong.
We don't live in an ideal world, so we have to deal with the world where we do live. And that means taking some steps to manage our risk of suffering criminal acts against us. The victim is not at fault, of course, but being not-at-fault doesn't take away the pain of having been victimized.
If you don't enjoy dealing with Retentions muppets, it's much easier to terminate a service in writing (or in the case of telephone service, by porting your number to a new provider). Check your terms and conditions for the official way to terminate, and you'll find the address there. Write them a letter and be done with it. There's no one to argue with you, that way.
Most ISPs have an "email only" product. They don't advertise it, but if you call, you'll probably find that for like $25/yr, they'll keep your email service alive for you.
You must also have that specific calculator to do the homework for the class.
There are smartphone emulators for all of the TI-8x calculators. No reason that you need the physical calculator.
So, to paraphrase Prof. Norm Matloff, is it stupid to buy expensive TI-8x milk when the R cow is free?
I don't know much about cows or milk, but if we could figure out a way to teach our kids R instead of how to use a TI-8x that they'll never touch again after graduation, we would be doing them a huge service.
Python has replaced Java for anything I used to do with it.
Python 2 or Python 3?
Unless you're targeting an embedded system with resource constraints, I see no reason not to implement it similar to the above.
It's straightforward. You're unlikely to introduce any bit-twiddling bugs. It wouldn't take more than a few minutes to write and debug. And, most importantly, it's readable for people who aren't accustomed to bitwise operations.
I thought about joining a while ago for the group health insurance plan, but they dropped that. So I did not join.
Because when someone asks a question, they rarely want to know what they asked.
This is absolutely true.
For today's interview, the role had no J2EE component to it at all. But the resume said "expert", so I have to ask the question. I need to know if we're being lied to.
Just to be clear, I don't think that I have seen an actual EJB in probably a decade. But when someone puts "expert" on his or her resume, then I need to ask about it.
There have been questions of my ability to do what is on my resume that are legit.
I do a lot of technical interviewing, and that is the whole point of a technical interview, to verify that you actually do possess the skills that you have claimed to possess.
It's not because you're black. It's because you're interviewing. I could tell so many stories of wild resume claims, you'd laugh.
Here's one from today, for an interviewee who was an "expert in J2EE".
Q: What are some different types of EJBs and how do they differ from one another?
A: [uncomfortable silence].
Q: Sorry, let's back up a bit. Tell me about your role in your last project that used J2EE.
A: Uhh, I think I made a JSP once in college before I left to go work at a startup.
As you might expect, his resume got filed away in the recycling bin.
I used to use firefox, but when they fired an executive for an ancient political contribution, I decided I couldn't use a browser made by that company. So now I use Chrome.
For the record, I don't even agree with the executive's cause that he contributed to. But firing an executive for making a political contribution is dangerous ground, so I can't support that.
You realize that there's more difference between your average man and your average woman than between your average NFL linebacker and your average man, right? (seriously, compare the stats some time - height, average bench strength, etc).
This is almost certainly wrong, by the way.
Have you ever watched draft combine footage? Those linebackers do 20 or even 30 reps of 225 lbs like it's nothing. Some linemen have a one rep max of 500 or 600 lbs. 400 lbs is common.
I don't know what the average man and woman can bench, but NFL linemen are insanely strong. One could easily pick me up and throw me across the room like a ragdoll. I could not do the same with my wife. I could pick her up and put her over my shoulder or something, but there is just no comparison to an NFL lineman.
I understand well that men are stronger than women on average. No dispute there. I just think that a lot of people don't realize just how insanely strong NFL linemen are. This is a huge part of why football is so dangerous.
Oh, a human definitely needs to be there for maintenance. You can't automate fixing up a screwup in the automation.
I just see no reason why maintenance windows have to be done at 1am. In today's world of redundancy and failover, there is just no reason for it. Every upgrade my team has done for as long as I can remember has been at 10am local time because we don't allow downtimes anyway. Why work at 1am?
Go around a data center and look at all the Oracle database instances that are single-instance...that's because Oracle rapes you on licensing
Then stop using Oracle if you can't afford RAC/GoldenGate/TAF/whatever. Use what you can afford in order to architect a proper redundant system. Running a database on a single instance is malpractice in 2014.
Even our network upgrades we do in the middle of the workday. After all testing is done, we just take a whole datacenter down and upgrade it. Once it's back online, we do the next datacenter until it's all done.
There's really no reason in 2014 to do 1am maintenance.
You should always have a competent tech on hand for maintenance tasks.
I agree with this, but who does maintenance at 1am anymore? What's the point in it? Users are worldwide, and 1am in the US prime business hours in Asia, so why bother patching/upgrading in the middle of the night?
I haven't done a late-night maintenance in at least a decade. It's all about rolling upgrades. Any problems? Rollback. Need to upgrade infrastructure? Take the entire datacenter offline and serve from your other datacenters. Every single upgrade I've done for as long as I can remember has been at 10am, which is the earliest I can get my lazy-ass junior devs to stumble into the office.
OP needs a process upgrade.
Only the most motivated people are going to go through all the hassle and work that it takes to actually get here, so of course they are more likely to be successful once they do.
Jewish immigrants after WWII came here because they had nowhere else to go, not because they wanted the hassle of moving to a country on the other side of the world where they didn't speak the language, didn't know anybody, etc. Their homes had been taken when they were transferred to death camps, and very few countries were willing to take them in. They seem to have turned out OK, though.
And less cooking liquid vs. non-pressurized applications since very little steam is lost once the cooker as achieved pressure. Once the desired pressure is reached, you turn the burner onto its lowest setting while the food cooks.
There are a few other things that add to pressure cooking's efficiency. This is from a person who uses a pressure cooker (me), not an expert in heat transfer nor any other discipline of physics.
1. Most pressure cooker applications other than soup are steaming applications, and since the pressure cooker traps the steam in, you don't use nearly as much liquid as you would in traditional cooking. Less liquid = less energy to heat it up.
2. Less loss of heat through the top. After a pressure cooker reaches the desired pressure, you actually turn the burner down to its lowest setting (or whatever the lowest setting is on your stove to maintain pressure--on my stove, it's the lowest).
That's all I can think of for now, but I will say that a pressure cooker is a neat cooking tool. Especially if you live in a hot climate, like I do. Most of my summer cooking is on the grill, naturally, but I use the pressure cooker a bit, too, and it doesn't heat my house up too badly.
However, ever since the Boston marathon bombing manhunt, the authorities don't like people buying pressure cookers.
That's just not true. I bought my pressure cooker after the Boston Marathon bombings, and nobody gave me a second look. Anyway, modern pressure cookers have multiple safety mechanisms so they don't go boom like your grandma's pressure cooker did.
I'd use jruby over grails. You get to code in ruby but run on the JVM. Best of both worlds.
Easier to find ruby developers than grails developers.