As long as it is applied evenly across all affects, a carbon tax will not harm the economy. The problem is taxing imports (allowed under the Constitution) and applying such a tax to even out costs.
I'm of the "GM might be ok if" variety. The biggest part of that "if" would be the banning of introducing external genetic information into an organism. Doing potentially naturally occurring mutations is one thing, bringing in genetic information from other organisms.... probably not a good idea in most cases.
which is why all my apps are blocked from location services, with 2 exceptions. Obviously, this has little impact on the phone service provider, since the very act of being connected will allow them to track you explicitly.
As for browser data, I don't do much browsing on my phone, the screen's too small for general browsing in comfort and it's missing a few features I use on my computers. If you were really paranoid, you could VPN all your connection info to your home system, unless, of course, you've bundled that with your provider, allowing them to still know exactly where you've gone and what you're doing.
Because most requirements are written rather poorly, and at that point, the BA will have to come in and weigh who's interpretation is correct, as they are the ones that wrote the requirement and should have a deep understanding of what was desired.
You have parts right and others not so right. The tester's job is to validate the business requirements are met, pure and simple. It's not the tester's responsibility, job, nor even a desired task to go "head to head" with a developer, ever. They test, file reports, and then the developers deal with meeting the goals. If there is a misunderstanding, then the BAs and leads get involved to clarify whatever requirements lead to the confusion. Generally someone, usually a PM type on larger projects, ensures that bugs etc get tracked and moved along.
Do you see someone arguing that a laptop is hard to type on? (Those super mini ultrabooks sure are) If they did you would probably be the first one to post a similar rebuttal.
For short responses to emails, tweets, chats, and oter similarly short things, the onscreen keyboard is more than sufficient on an iPad. Hell, people use those miniscule on screen keyboards on their phones to do the same, and apparently they are not worthy of complaints.
If you're going to type a novel or something else "long", you might want a little more feedback, and one of those BT keyboards would be just the thing. They'll work for some of those phones, too.
Depends on the product though. But as you said, there is very little interesting work but what if that little piece of interesting work turns out to be the most crucial part of the project? For example, 99% of Google could be made by anyone but the magic is in the PageRank which is probably 1% of it. In the end, what was the difference between Google and it's competitors like Yahoo, Altavista and other search engines? That 1% in PageRank.
Seems like we agree on most aspects there. For page rank, I believe that is not even that interesting. It was merely one of several ways to rank results, and it started out very simplistically and was refined over a long period, as in years, before it began to be corrupted by SEO efforts and advertising drivers (the latter is just my opinion, but it seems valid)
Theoretically, hiring a PhD would give you some guarantee about what the programmer is capable of doing...
Funny enough, a PhD is almost an automatic disqualification, as is "currently working on one". Why? Because in general someone that has gone through that amount of theoretical work generally has little interest in doing actual grunt work required to get a product out. And, as most developers will attest, 99% of programming is pretty much grunt work. There's very little "interesting" work going on, as that is usually in the frameworks you use, or attempting to work around some bug in a framework. So if your job is creating frameworks, graphics engines. OS kernels, or the like, then you might benefit from a PhD or two being on the team. Otherwise, unless they are a very special kind of person, not so much.
Artists have always made money by touring and the recordings have never given them much income
This would be because the RIAA members (the distributors) have made it an art form to churn through artists and some not quite artists to rake in all their money, sidelining anyone that doesn't sign on their dotted line.
Posting to undo bad mod. This is definitely the most valid point you can make against DRM - music's really never had it, nor was it ever effective. And yet it still thrives.
That's funny, truly funny. I ran XP for years. No AV. Browsed the web at will. 0 infections after 5 years when I installed the latest AV package at the time just for kicks. Of course, I disabled auto-update, no flash, and had Firefox with noscript installed as my primary browser, along with no java plugin for the browser either, although I did run java, lots of java, even some.NET. I should also mention I stripped most of the unnecessary crap out of the OS, trimmed it way down and slipstreamed my own configuration. All that work and I still had something less secure than an OOB Ubuntu or OS X desktop. At the time I needed an XP desktop, once alternatives got good enough.... bye bye windows.
I don't recall what I used for PDF, maybe a really old version of reader that had only PDF viewing as a function? It's been way too long ago to remember all that. But yes, OOB, Windows XP prior to SP3 was a honeypot just waiting for the sting of that first packet....
Even though I admit using XP, I've been looking for alternatives during that entire time. I first dabbled with Linux in 94, playing with various releases throughout the years, using them for servers, but desktops? Ubuntu is close, but I've already got a solid unix distro, so my impetus for changing to a Linux desktop is really low.
Teenagers have surprisingly limited vision. Depending upon where they are and what their interests are, they might even be completely unaware that a meteor almost hit earth last month, or that a new pope was just selected, etc.
I've seen one of those solutions in progress - the system was so screwed by bad design that the 8-proc servers couldn't handle the load of 1000 users. It wound up being a full rewrite, after which we could handle 5K users per smaller server, with multiple servers scaling out, and the original DB hardware handled more than 100K users, whereas the DB for the original system couldn't scale up fast enough. You should always make sure to practice good design, it only costs you a little time to think, which is a tiny tiny fraction of the time/cost/effort for what's needed in comparison to rewrites.
This does not mean that you should over think the problem and spend years on design. I've mentioned before, there's an almost cookie-cutter approach to the server side functionality for pretty much all apps, with a few choices to accomplish your desired path of scalability.
I have built and am still building platforms scaling to tens of thousands of concurrent users. I have been doing this for more than a decade. It's not exactly difficult to do so, what is difficult is making sure you don't use the latest gee whiz widget that does things in a non-scalable way, or have developers do short-cuts under the covers that cause issues. To do so successfully requires understanding your entire selected stack and designing your layers to avoid as many bottle necks as possible. Another big one is to design those layers, because that's how you'll be scaling your app. You'll also have to make some choices: High Performance, High Availability, High Reliability, pick any two, was what we used to say. At 2 companies, we did all 3. Both were bought, hence I moved on. Since 2000, they have all been at least partially Java based.
Having been at several companies that do define scalability as an initial concern (ok, in one case being forced to realize it;) Let's say that ignoring scalability and bolting it on later has the same effect as ignoring security and attempting to bolt that on later. You wind up sticking bandaids on bandaids, and that always leads to the same end.
If gun control was responsible for saving just one life then it would be worth it. Violence isn't going away and you're right to suggest that the impact might be limited but that doesn't mean that it shouldn't be done. In the 5-10 years you suggest this law might be effective, more needs to be done. I don't see the short term potential as a reason for doing nothing though.
If knife control was responsible for saving one life....
If candy control was responsible for saving one life....
You would if you were selected out of a group because of your race, gender, religious beliefs, etc and then attacked because the attacker felt you and all your ilk should suffer. Or are you saying in that case the attacker should get off scott free because maybe society made him do it?
A) reduce the work week gradually. 38 hours, then 36, you get the idea.
B) have basic healthcare provided, This means preventative care, ER visits, and some relatively well-known and general diseases. If you want cancer, chronic diseases, etc covered, you'll need to pay for supplemental insurance, just like today. This would significantly lower the bill on businesses hiring individuals
having knowledge of more than 20 companies that all used Struts at one time, some still do, I'd say that 0 percent adoption is telling. Several went JSF, others started using SpringMVC. Anecdotal, I know, but in my entire circle of people I know, not a single one has used Struts 2 beyond a distasteful POC, provided they got past the initial documentation.
Follow that with your own comment - it may not be worse, but it's not better. And that was enough to arrive DOA for many.
Yeah, EMS/EMX? was essential to your configuration for max low memory. Once you went through the pain of creating that boot disk, though, you were sitting pretty for virtually every DOS game ever, except for those that came with their own sound driver non-standard configurations, those were truly a pain.
Lemmings.... I still have those in a box, next to Populous. Also Humans. And Populous. All great games.
Slashdot Mirror
As long as it is applied evenly across all affects, a carbon tax will not harm the economy. The problem is taxing imports (allowed under the Constitution) and applying such a tax to even out costs.
I'm of the "GM might be ok if" variety. The biggest part of that "if" would be the banning of introducing external genetic information into an organism. Doing potentially naturally occurring mutations is one thing, bringing in genetic information from other organisms.... probably not a good idea in most cases.
I know, we'll call it Soylent Green.
You missed the largest wind farms of all, in Texas, a bright red state. The NE nor CA have sole dibs on alternative energy.
which is why all my apps are blocked from location services, with 2 exceptions. Obviously, this has little impact on the phone service provider, since the very act of being connected will allow them to track you explicitly.
As for browser data, I don't do much browsing on my phone, the screen's too small for general browsing in comfort and it's missing a few features I use on my computers. If you were really paranoid, you could VPN all your connection info to your home system, unless, of course, you've bundled that with your provider, allowing them to still know exactly where you've gone and what you're doing.
Because most requirements are written rather poorly, and at that point, the BA will have to come in and weigh who's interpretation is correct, as they are the ones that wrote the requirement and should have a deep understanding of what was desired.
You have parts right and others not so right. The tester's job is to validate the business requirements are met, pure and simple. It's not the tester's responsibility, job, nor even a desired task to go "head to head" with a developer, ever. They test, file reports, and then the developers deal with meeting the goals. If there is a misunderstanding, then the BAs and leads get involved to clarify whatever requirements lead to the confusion. Generally someone, usually a PM type on larger projects, ensures that bugs etc get tracked and moved along.
Do you see someone arguing that a laptop is hard to type on? (Those super mini ultrabooks sure are) If they did you would probably be the first one to post a similar rebuttal.
For short responses to emails, tweets, chats, and oter similarly short things, the onscreen keyboard is more than sufficient on an iPad. Hell, people use those miniscule on screen keyboards on their phones to do the same, and apparently they are not worthy of complaints.
If you're going to type a novel or something else "long", you might want a little more feedback, and one of those BT keyboards would be just the thing. They'll work for some of those phones, too.
Depends on the product though. But as you said, there is very little interesting work but what if that little piece of interesting work turns out to be the most crucial part of the project? For example, 99% of Google could be made by anyone but the magic is in the PageRank which is probably 1% of it. In the end, what was the difference between Google and it's competitors like Yahoo, Altavista and other search engines? That 1% in PageRank.
Seems like we agree on most aspects there. For page rank, I believe that is not even that interesting. It was merely one of several ways to rank results, and it started out very simplistically and was refined over a long period, as in years, before it began to be corrupted by SEO efforts and advertising drivers (the latter is just my opinion, but it seems valid)
Theoretically, hiring a PhD would give you some guarantee about what the programmer is capable of doing...
Funny enough, a PhD is almost an automatic disqualification, as is "currently working on one". Why? Because in general someone that has gone through that amount of theoretical work generally has little interest in doing actual grunt work required to get a product out. And, as most developers will attest, 99% of programming is pretty much grunt work. There's very little "interesting" work going on, as that is usually in the frameworks you use, or attempting to work around some bug in a framework. So if your job is creating frameworks, graphics engines. OS kernels, or the like, then you might benefit from a PhD or two being on the team. Otherwise, unless they are a very special kind of person, not so much.
Artists have always made money by touring and the recordings have never given them much income
This would be because the RIAA members (the distributors) have made it an art form to churn through artists and some not quite artists to rake in all their money, sidelining anyone that doesn't sign on their dotted line.
Posting to undo bad mod. This is definitely the most valid point you can make against DRM - music's really never had it, nor was it ever effective. And yet it still thrives.
That's funny, truly funny. I ran XP for years. No AV. Browsed the web at will. 0 infections after 5 years when I installed the latest AV package at the time just for kicks. Of course, I disabled auto-update, no flash, and had Firefox with noscript installed as my primary browser, along with no java plugin for the browser either, although I did run java, lots of java, even some .NET. I should also mention I stripped most of the unnecessary crap out of the OS, trimmed it way down and slipstreamed my own configuration. All that work and I still had something less secure than an OOB Ubuntu or OS X desktop. At the time I needed an XP desktop, once alternatives got good enough.... bye bye windows.
I don't recall what I used for PDF, maybe a really old version of reader that had only PDF viewing as a function? It's been way too long ago to remember all that. But yes, OOB, Windows XP prior to SP3 was a honeypot just waiting for the sting of that first packet....
Even though I admit using XP, I've been looking for alternatives during that entire time. I first dabbled with Linux in 94, playing with various releases throughout the years, using them for servers, but desktops? Ubuntu is close, but I've already got a solid unix distro, so my impetus for changing to a Linux desktop is really low.
Teenagers have surprisingly limited vision. Depending upon where they are and what their interests are, they might even be completely unaware that a meteor almost hit earth last month, or that a new pope was just selected, etc.
I've seen one of those solutions in progress - the system was so screwed by bad design that the 8-proc servers couldn't handle the load of 1000 users. It wound up being a full rewrite, after which we could handle 5K users per smaller server, with multiple servers scaling out, and the original DB hardware handled more than 100K users, whereas the DB for the original system couldn't scale up fast enough. You should always make sure to practice good design, it only costs you a little time to think, which is a tiny tiny fraction of the time/cost/effort for what's needed in comparison to rewrites.
This does not mean that you should over think the problem and spend years on design. I've mentioned before, there's an almost cookie-cutter approach to the server side functionality for pretty much all apps, with a few choices to accomplish your desired path of scalability.
exactly! Building to be scalable is not all that hard, but it does require a level of understanding.
I have built and am still building platforms scaling to tens of thousands of concurrent users. I have been doing this for more than a decade. It's not exactly difficult to do so, what is difficult is making sure you don't use the latest gee whiz widget that does things in a non-scalable way, or have developers do short-cuts under the covers that cause issues. To do so successfully requires understanding your entire selected stack and designing your layers to avoid as many bottle necks as possible. Another big one is to design those layers, because that's how you'll be scaling your app. You'll also have to make some choices: High Performance, High Availability, High Reliability, pick any two, was what we used to say. At 2 companies, we did all 3. Both were bought, hence I moved on. Since 2000, they have all been at least partially Java based.
Having been at several companies that do define scalability as an initial concern (ok, in one case being forced to realize it ;) Let's say that ignoring scalability and bolting it on later has the same effect as ignoring security and attempting to bolt that on later. You wind up sticking bandaids on bandaids, and that always leads to the same end.
I'd vote for Direct-8.
Yep, John Carmack must not know what he's talking about.
If gun control was responsible for saving just one life then it would be worth it. Violence isn't going away and you're right to suggest that the impact might be limited but that doesn't mean that it shouldn't be done. In the 5-10 years you suggest this law might be effective, more needs to be done. I don't see the short term potential as a reason for doing nothing though.
If knife control was responsible for saving one life....
If candy control was responsible for saving one life....
If free speech control was.....
You would if you were selected out of a group because of your race, gender, religious beliefs, etc and then attacked because the attacker felt you and all your ilk should suffer. Or are you saying in that case the attacker should get off scott free because maybe society made him do it?
A) reduce the work week gradually. 38 hours, then 36, you get the idea.
B) have basic healthcare provided, This means preventative care, ER visits, and some relatively well-known and general diseases. If you want cancer, chronic diseases, etc covered, you'll need to pay for supplemental insurance, just like today. This would significantly lower the bill on businesses hiring individuals
having knowledge of more than 20 companies that all used Struts at one time, some still do, I'd say that 0 percent adoption is telling. Several went JSF, others started using SpringMVC. Anecdotal, I know, but in my entire circle of people I know, not a single one has used Struts 2 beyond a distasteful POC, provided they got past the initial documentation.
Follow that with your own comment - it may not be worse, but it's not better. And that was enough to arrive DOA for many.
Yeah, EMS/EMX? was essential to your configuration for max low memory. Once you went through the pain of creating that boot disk, though, you were sitting pretty for virtually every DOS game ever, except for those that came with their own sound driver non-standard configurations, those were truly a pain.
Lemmings.... I still have those in a box, next to Populous. Also Humans. And Populous. All great games.