Engineers don't apprentice. I don't understand this.
I beg to differ. There may not be a formal apprenticeship program like a doctor's residency program, but no company that hires engineers takes a newly minted E.E. or M.E. and hands him a project to do. Said new hire will be part of a team, or tasked to do the work on some standardized kind of part that will then be reviewed by the project lead. My cousin graduated this last May with her ChemE degree and went to work doing the exact same job she did as an intern last summer, reporting to the same people. The only difference is she needs less hand holding and does more of the work on her own.
Not only had I been born, I had written a Basic program to generate D&D character stats by 1980. Yes, my PUBLIC elementary school had some forward thinking administrators.
You have the right to bear arms, the civil rights, why can't you have "the right to broadband access" too?
You misunderstand the definition of "right." In the US Constitution it means a person has the choice to do something free from government interference. You *may* own a gun, if you so desire. You may say, or write, whatever you wish without restriction. You may associate with whomever you choose. Nowhere in there does it say that the method to exercise that right will be provided, only that it is allowed without interference. I am free to publish a newspaper but I have to pay for it. A "right" to something that requires delivery of a service or product places everybody but the receiver in a position of slavery. If a person has a "right" to medical care, some doctor or medical profession MUST provide that service. If a person has a "right" to broadband, some company must string wire, another must provision access to their networking hardware and yet another must provide electricity to run it all.
I do brisket cooks on my Big Green Egg that require me to get up periodically throughout the night. I have a WRT54G I am not using that I will be converting to a BBQ controller posthaste.
The point of my post is that with electronics, one really cannot know what *might* happen. Planes are going to "fly-by-wire" so as long as the control surfaces on the aircraft in which I am flying can be actuated by a computer I would like said computer to be as free from interference as possible.
Probably, not every single computer in the OP's work needs to work with a Kinect.
I would hope so. I worry about any accounting system operated by gestures. I would also prefer to not walk in the front door and see the receptionist waving her arms around.
I fly C182's and A36 Bonanzas and have had this exact same thing happen to me. When I read someone like chemicaldave above dismissing the statement because the evidence is only anecdotal I can only shake my head. I'm responsible for me and up to 3 other people and the idea of my iPhone messing up my ability to fly safely scares the crap out of me. The attorneys for the big airlines must have to take drugs to sleep for how much they have to worry about a plane full of people going down because some new gadget interfered with the plane on takeoff, the most dangerous part of any flight.
The problem is that the person making that statement didn't get it quite right. From my professor of Managerial Economics: "The job of management is the LONG TERM maximization of shareholder wealth." This means that selling one's manufacturing equipment for a short term gain doesn't make sense because next year income will be zero. Likewise, it benefits the long term view for employer and employee to have cordial, versus adversarial, relations because the most productive, innovative workforce is the one that wants to come to work each each day. As a shareholder, I would hope that the management can wring every cent to the bottom line they can. I also expect, however, that they will not open the company to a future lawsuit in the process.
I am pretty sure one of the worst decisions that could ever possibly be made would be to get into a conventional war with a country with an overpopulation problem that is only a couple of hundred miles away by boat. The Chinese could just start sending ships full of civilians to Japan and overwhelm their infrastructure. The Japanese couldn't shoot unarmed civilians; they would have to arrest and detain them. China could collapse Japan without firing a shot.
I did this once and hosed a production Informix system. We had over 100 external users call in before it was realized and fixed. Fortunately, I did it because my manager told me to so I kept my job and she was reprimanded for A) changing production and B) asking someone else to do it and not doing it herself. I learned my lesson and in the subsequent 10 years have never modified a production system without thorough dev testing first.
hearing your buddies drop the f-bomb in the next room
This, imho, was one of the best things about LAN parties. Several friends and I used to play Command & Conquer at one guy's office after work. The room was divided by low walls and we all had speakers so occasionally you'd hear the dreaded words "A-Bomb prepping" followed by "A-Bomb ready." The room would get silent while everyone waited to see whose main building was going to get destroyed followed by !#$@% when it happened.
I'll give you bad, or maybe even "one of..." but remember, Battlefield Earth does exists. As the leading candidate for "Worst Sci-Fi Movie of the 21st Century" ID4 is Casablanca in comparison. (By the way, this is an uninformed opinion. I am not willing to sit through Battlefield Earth to confirm.)
The essential facts of the case are this: it is foolish to ride in a car with a liquid in one's lap of any temperature. This does not stop most people from doing it, but one never knows when a car will need to swerve or hit a bump that will cause said liquid to spill. This act of spillage will introduce an extreme unexpected element into the situation. Should the driver experience this an accident is entirely likely. For a passenger it is at best an embarrassment.
I did go and read the details and have retracted my characterization of the victim as a "ho." I will maintain, however, my opinion that she is as much at fault as the restaurant. EVERY adult in the world knows coffee is hot. That fact alone should have told her that special care needs to be taken every time coffee is ordered "to-go." It is unfortunate she was hurt. I was almost killed because I did something I knew I shouldn't do. I, at least, had the civility to admit my responsibility even though lawsuits could have been filed.
After reading further, I withdraw my characterization of this lady as a "ho." I will continue to believe that anyone who drives with a hot liquid in their lap, in a car, is foolish and that this injury was in part her responsiblity, regardless of whatever warning McDonald's was or wasn't issued concerning the temperature of their coffee.
Perhaps the Corp could file suit for him being an idiot? They've only got about 50 years worth of evidence of people using these devices safely and properly without injury backing them up. And God knows how anyone ever survived before we had "Saw Stop" technology...
People have hundreds of years of knowing that hot liquids can burn you and that didn't stop that ho from winning a verdict against MickeyD's for burning herself with their coffee.
I don't think "never" should be used in this case. My understanding of the subject is lacking, but I believe that some of the appeal of quantum computing is that a qbit computer can represent all states at once. While I don't know how the q-computer can be used to test against the encrypted drive, if the alternate timeframe is 10^59th years my guess is they will figure out how to use the q-computer for this before then. While it is not a traditional "test, increment, test again" brute force methodology, a device that can test everything at once has as much chance of failure as the person who buys all the possible lottery picks.
This has been my experience as well. Though I don't have a CS degree, I had enough formal programming work as an Engineering major to understand how to do it mostly right. When I was lead Internet developer for a computer sales company I ran into a large number of developers who excelled at finding things online that could do part of their overall goal and then massaging the outputs to be able to string them together. Yes, the solutions worked but looking at the code reminded me of a car built by collecting parts from every manufacturer and forcing them to work together with a bunch of adapter kits.
The worst problem with these solutions is that they are virtually unchangeable. The code from each has been so massaged to feed output to the next piece that all flexibility to extend or change is lost. Asking the "developer" to change his solution is effectively asking for a complete rewrite.
When one hears the generalization that small companies are more agile, this is exactly the kind of thing being referenced. A company that makes 200 cars a year can investigate and utilize different technologies without much hassle. Just imagine for a moment the supply chain changes required to change an engine component on the Ford F-150 truck.
I used to have a collection of old hardware and tried doing this a couple times. You are going to find that it is so incredibly slow that whatever satifaction you got from getting it to work will be more than cancelled by the disappointment in the performance. I tried installing a couple Linux flavors on a Dual Pentium Pro 200 with 1 GB of RAM, a computer that is light years ahead of your i486 and was quite depressed about how poorly it performed. The fact is that successive generations of CPU's really smoke the previous ones, and two generations is too big a gap.
Save yourself the aggravation.
Slashdot Mirror
I realize it isn't termite fishing with a stick like monkeys do but it is certainly manipulation of an object for the animal's benefit.
Engineers don't apprentice. I don't understand this.
I beg to differ. There may not be a formal apprenticeship program like a doctor's residency program, but no company that hires engineers takes a newly minted E.E. or M.E. and hands him a project to do. Said new hire will be part of a team, or tasked to do the work on some standardized kind of part that will then be reviewed by the project lead. My cousin graduated this last May with her ChemE degree and went to work doing the exact same job she did as an intern last summer, reporting to the same people. The only difference is she needs less hand holding and does more of the work on her own.
Getting it from seawater is an idea that I've heard mentioned a few times and if that were possible
Hartson Brant figured this out back in 1947. (Just checking to see how many people know this reference.)
Not only had I been born, I had written a Basic program to generate D&D character stats by 1980. Yes, my PUBLIC elementary school had some forward thinking administrators.
You have the right to bear arms, the civil rights, why can't you have "the right to broadband access" too?
You misunderstand the definition of "right." In the US Constitution it means a person has the choice to do something free from government interference. You *may* own a gun, if you so desire. You may say, or write, whatever you wish without restriction. You may associate with whomever you choose. Nowhere in there does it say that the method to exercise that right will be provided, only that it is allowed without interference. I am free to publish a newspaper but I have to pay for it. A "right" to something that requires delivery of a service or product places everybody but the receiver in a position of slavery. If a person has a "right" to medical care, some doctor or medical profession MUST provide that service. If a person has a "right" to broadband, some company must string wire, another must provision access to their networking hardware and yet another must provide electricity to run it all.
Calling Andrew Wiggen...
I do brisket cooks on my Big Green Egg that require me to get up periodically throughout the night. I have a WRT54G I am not using that I will be converting to a BBQ controller posthaste.
The point of my post is that with electronics, one really cannot know what *might* happen. Planes are going to "fly-by-wire" so as long as the control surfaces on the aircraft in which I am flying can be actuated by a computer I would like said computer to be as free from interference as possible.
Probably, not every single computer in the OP's work needs to work with a Kinect.
I would hope so. I worry about any accounting system operated by gestures. I would also prefer to not walk in the front door and see the receptionist waving her arms around.
I fly C182's and A36 Bonanzas and have had this exact same thing happen to me. When I read someone like chemicaldave above dismissing the statement because the evidence is only anecdotal I can only shake my head. I'm responsible for me and up to 3 other people and the idea of my iPhone messing up my ability to fly safely scares the crap out of me. The attorneys for the big airlines must have to take drugs to sleep for how much they have to worry about a plane full of people going down because some new gadget interfered with the plane on takeoff, the most dangerous part of any flight.
The problem is that the person making that statement didn't get it quite right. From my professor of Managerial Economics: "The job of management is the LONG TERM maximization of shareholder wealth." This means that selling one's manufacturing equipment for a short term gain doesn't make sense because next year income will be zero. Likewise, it benefits the long term view for employer and employee to have cordial, versus adversarial, relations because the most productive, innovative workforce is the one that wants to come to work each each day. As a shareholder, I would hope that the management can wring every cent to the bottom line they can. I also expect, however, that they will not open the company to a future lawsuit in the process.
I am pretty sure one of the worst decisions that could ever possibly be made would be to get into a conventional war with a country with an overpopulation problem that is only a couple of hundred miles away by boat. The Chinese could just start sending ships full of civilians to Japan and overwhelm their infrastructure. The Japanese couldn't shoot unarmed civilians; they would have to arrest and detain them. China could collapse Japan without firing a shot.
I did this once and hosed a production Informix system. We had over 100 external users call in before it was realized and fixed. Fortunately, I did it because my manager told me to so I kept my job and she was reprimanded for A) changing production and B) asking someone else to do it and not doing it herself. I learned my lesson and in the subsequent 10 years have never modified a production system without thorough dev testing first.
hearing your buddies drop the f-bomb in the next room
This, imho, was one of the best things about LAN parties. Several friends and I used to play Command & Conquer at one guy's office after work. The room was divided by low walls and we all had speakers so occasionally you'd hear the dreaded words "A-Bomb prepping" followed by "A-Bomb ready." The room would get silent while everyone waited to see whose main building was going to get destroyed followed by !#$@% when it happened.
the worst sci-fi movie ever
I'll give you bad, or maybe even "one of..." but remember, Battlefield Earth does exists. As the leading candidate for "Worst Sci-Fi Movie of the 21st Century" ID4 is Casablanca in comparison. (By the way, this is an uninformed opinion. I am not willing to sit through Battlefield Earth to confirm.)
The essential facts of the case are this: it is foolish to ride in a car with a liquid in one's lap of any temperature. This does not stop most people from doing it, but one never knows when a car will need to swerve or hit a bump that will cause said liquid to spill. This act of spillage will introduce an extreme unexpected element into the situation. Should the driver experience this an accident is entirely likely. For a passenger it is at best an embarrassment. I did go and read the details and have retracted my characterization of the victim as a "ho." I will maintain, however, my opinion that she is as much at fault as the restaurant. EVERY adult in the world knows coffee is hot. That fact alone should have told her that special care needs to be taken every time coffee is ordered "to-go." It is unfortunate she was hurt. I was almost killed because I did something I knew I shouldn't do. I, at least, had the civility to admit my responsibility even though lawsuits could have been filed.
After reading further, I withdraw my characterization of this lady as a "ho." I will continue to believe that anyone who drives with a hot liquid in their lap, in a car, is foolish and that this injury was in part her responsiblity, regardless of whatever warning McDonald's was or wasn't issued concerning the temperature of their coffee.
Perhaps the Corp could file suit for him being an idiot? They've only got about 50 years worth of evidence of people using these devices safely and properly without injury backing them up. And God knows how anyone ever survived before we had "Saw Stop" technology...
People have hundreds of years of knowing that hot liquids can burn you and that didn't stop that ho from winning a verdict against MickeyD's for burning herself with their coffee.
I don't think "never" should be used in this case. My understanding of the subject is lacking, but I believe that some of the appeal of quantum computing is that a qbit computer can represent all states at once. While I don't know how the q-computer can be used to test against the encrypted drive, if the alternate timeframe is 10^59th years my guess is they will figure out how to use the q-computer for this before then. While it is not a traditional "test, increment, test again" brute force methodology, a device that can test everything at once has as much chance of failure as the person who buys all the possible lottery picks.
the tendency of the car to explode upon the slightest impact
Didn't they already install this technology in the Ford Pinto?
This has been my experience as well. Though I don't have a CS degree, I had enough formal programming work as an Engineering major to understand how to do it mostly right. When I was lead Internet developer for a computer sales company I ran into a large number of developers who excelled at finding things online that could do part of their overall goal and then massaging the outputs to be able to string them together. Yes, the solutions worked but looking at the code reminded me of a car built by collecting parts from every manufacturer and forcing them to work together with a bunch of adapter kits.
The worst problem with these solutions is that they are virtually unchangeable. The code from each has been so massaged to feed output to the next piece that all flexibility to extend or change is lost. Asking the "developer" to change his solution is effectively asking for a complete rewrite.
The spice and how the worms fit in with it (which may not have even been related in the first book come to think of it).
IIRC, there is an appendix in "Dune" by Pardot Kynes discussing the triangle of worms, little makers and pre-spice mass that explains everything.
When one hears the generalization that small companies are more agile, this is exactly the kind of thing being referenced. A company that makes 200 cars a year can investigate and utilize different technologies without much hassle. Just imagine for a moment the supply chain changes required to change an engine component on the Ford F-150 truck.
The first rule of Fight Club is: you do not talk about Fight Club.
I used to have a collection of old hardware and tried doing this a couple times. You are going to find that it is so incredibly slow that whatever satifaction you got from getting it to work will be more than cancelled by the disappointment in the performance. I tried installing a couple Linux flavors on a Dual Pentium Pro 200 with 1 GB of RAM, a computer that is light years ahead of your i486 and was quite depressed about how poorly it performed. The fact is that successive generations of CPU's really smoke the previous ones, and two generations is too big a gap. Save yourself the aggravation.