There's a warning right there in the org.apache.commons.collections.Limb.Foot documentation about calling the doShoot() method with unsigned copies of org.apache.http.client.Bullet.
No. But some do, for certain definitions of 'faulty'. Not understanding default settings or the limitations of the underlying mathematical model are two common mistakes some engineers make. The software isn't always 'bad' per se. It's just being used in a manner not anticipated by its designers. On the other hand, some of it is just plain bad.
What?!?! Put down that pencil and back away from the drafting table. Slowly.
Those that are not licensed may be employees, working on a product design for a company in a state with an industrial exemption AND the work is either supervised by a PE or not subject to state laws/regulations. Civil engineers tend to work exclusively in regulated areas that involve public safety. So they are overwhelmingly licensed. But a significant number of EEs work in similarly regulated areas and must be licensed as well.
Additionally, construction codes and regulations aside, most states require licenses for any engineer offering services to the public as a sole proprietor, partner or corporation.
I was working for the local utility when we made the switch from mercury vapor to sodium vapor lighting. The screams and howls about poor color rendition and visibility problems almost made us switch back.
Sodium vapor lamps may be more efficient. But just ask the cops who were around at the time of the switchover. Every hit-and-run vehicle reported was a muddy brown color and every suspect was black.
It is (to a degree) in the United States as well. With one loophole: The industrial exemption. On a state by state basis (engineers are licensed by states), some allow engineering done by firms' employees solely for the purpose of manufacturing a product to be exempt from licensing requirement. Some do not.
Also, on a state by state basis, the interpretation of 'performing work under the supervision of a licensed engineer' is interpreted broadly. I've worked for utilities where the senior engineer on site was a burned out meter reader and the licensed PE doing the review sat in an office a hundred miles away and often didn't see the drawings until long after the work was done.
This is a good point. But it's not a topic you want to raise around the engineering sofware community. Technically, for me (a licensed engineer) to use your product, it should be written and tested to requirements created by professional engineers. And the underlying algorithms and code should be available for us to examine (not quite open source). But try running that by any one of the big software vendors and they will sh*t themselves. In fact, some of it requires NDAs to be signed. Some utility SCADA and power flow apps were notorious for this. Not because they wanted to protect some valuable IP, but because the software was crap and they didn't want users comparing notes.
In addition to one I carry (Pickett Model N 3-T) I have a decent collection, including some special purpose 'slide rules' or circular calculators. Like an Air Force MB-2A. And a couple of (now declassified) missile and nuclear weapons effects calculators.
Moreover, as you pointed out, there's nothing stopping anyone from creating additional sets of keys since key creation is decentralized and isn't linked to anything in the real world,
This is where the key generation would have to include the voter registration authority. Some sort of one way hash to anomymize a voter's actual identity. But based on some physical identification* such that repeated applications for new keys would reveal that the same applicant was asking for multiples. Yes, this could be due to them losing their key. But it would be trivially easy to inspect the voting chain for mutiple entries based on the unique ID hash.
*Inevitably, this won't work. Because any attempt to require an ID will be met by the hobo brigade. Who may not actually intend to commit voter fraud. But they just can't remember which name they are using today after their latest drinking binge.
Chain of trust. Every vote is represented as a transaction in a block chain*. So it won't matter if copies of the storage media are floating around. If the chain doesn't trace back to an original (authenticated) state, it must be fake. I'm not a crypto, Bitcoin wizard. But I'm sure some smart people can work out the details.
*Not necessarily _the_ Bitcoin blockchain. But one created along the same principles by election authorities.
Music/podcasts are great for training but generally frowned upon in actual races,
It might be better to seperate the music from the other functions. Get something like an iPod Shuffle and do the rest with a GPS/monitor device. For a bit more bulk than a watch, a Garmin eTrex 30 will do GPS, altimiter and talk to an external heart rate monitor (and record your data as you go). I know some people who will cycle a course and download the elevation data into a programmable stationary cycle. The recorded data 'duplicates' the course elevation for trining purposes.
There's the target aquisition and tracking problem. That could be an issue at night when drones can fly GPS or inertial guidance (night/day doesn't matter to a drone).
Something like this. Although the air marshals carry a P229 Sig Sauer chambered for.357 Sig rounds (a 10mm auto shell necked down to a.357 bullet). So, not really concerned with overpenetration or blowing out a window.
Slashdot Mirror
Only if you've got Google Fiber.
There's a warning right there in the org.apache.commons.collections.Limb.Foot documentation about calling the doShoot() method with unsigned copies of org.apache.http.client.Bullet.
Can engineers pass the blame faulty software?
No. But some do, for certain definitions of 'faulty'. Not understanding default settings or the limitations of the underlying mathematical model are two common mistakes some engineers make. The software isn't always 'bad' per se. It's just being used in a manner not anticipated by its designers. On the other hand, some of it is just plain bad.
for the oil trains.
High pressure sodium has a CRI of 20 to 25. 'White' LEDs can be around 60 or better. Which is still crap, but usable.
Electrical Engineers ( No License in the U.S.)
What?!?! Put down that pencil and back away from the drafting table. Slowly.
Those that are not licensed may be employees, working on a product design for a company in a state with an industrial exemption AND the work is either supervised by a PE or not subject to state laws/regulations. Civil engineers tend to work exclusively in regulated areas that involve public safety. So they are overwhelmingly licensed. But a significant number of EEs work in similarly regulated areas and must be licensed as well.
Additionally, construction codes and regulations aside, most states require licenses for any engineer offering services to the public as a sole proprietor, partner or corporation.
On the other hand, we have noticed an increase in sightings of Halley's Comet by Comcast customer service personnel.
Also much easier on the eyes while night driving.
How soon they forget.
I was working for the local utility when we made the switch from mercury vapor to sodium vapor lighting. The screams and howls about poor color rendition and visibility problems almost made us switch back.
Sodium vapor lamps may be more efficient. But just ask the cops who were around at the time of the switchover. Every hit-and-run vehicle reported was a muddy brown color and every suspect was black.
I want to see this phrase re-written in the active voice.
"Mistakes were made." "A police-involved shooting."
The language is full of these. Take a number and wait your turn.
It is (to a degree) in the United States as well. With one loophole: The industrial exemption. On a state by state basis (engineers are licensed by states), some allow engineering done by firms' employees solely for the purpose of manufacturing a product to be exempt from licensing requirement. Some do not.
Also, on a state by state basis, the interpretation of 'performing work under the supervision of a licensed engineer' is interpreted broadly. I've worked for utilities where the senior engineer on site was a burned out meter reader and the licensed PE doing the review sat in an office a hundred miles away and often didn't see the drawings until long after the work was done.
This is a good point. But it's not a topic you want to raise around the engineering sofware community. Technically, for me (a licensed engineer) to use your product, it should be written and tested to requirements created by professional engineers. And the underlying algorithms and code should be available for us to examine (not quite open source). But try running that by any one of the big software vendors and they will sh*t themselves. In fact, some of it requires NDAs to be signed. Some utility SCADA and power flow apps were notorious for this. Not because they wanted to protect some valuable IP, but because the software was crap and they didn't want users comparing notes.
Nixie tubes. Meh.
How about an HP 9100? Programmable, scientific functions, RPN. And no integrated circuits (all discrete component logic).
In addition to one I carry (Pickett Model N 3-T) I have a decent collection, including some special purpose 'slide rules' or circular calculators. Like an Air Force MB-2A. And a couple of (now declassified) missile and nuclear weapons effects calculators.
Also known among pilots as prayer wheels.
Moreover, as you pointed out, there's nothing stopping anyone from creating additional sets of keys since key creation is decentralized and isn't linked to anything in the real world,
This is where the key generation would have to include the voter registration authority. Some sort of one way hash to anomymize a voter's actual identity. But based on some physical identification* such that repeated applications for new keys would reveal that the same applicant was asking for multiples. Yes, this could be due to them losing their key. But it would be trivially easy to inspect the voting chain for mutiple entries based on the unique ID hash.
*Inevitably, this won't work. Because any attempt to require an ID will be met by the hobo brigade. Who may not actually intend to commit voter fraud. But they just can't remember which name they are using today after their latest drinking binge.
Last message received: "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn".
Chain of trust. Every vote is represented as a transaction in a block chain*. So it won't matter if copies of the storage media are floating around. If the chain doesn't trace back to an original (authenticated) state, it must be fake. I'm not a crypto, Bitcoin wizard. But I'm sure some smart people can work out the details.
*Not necessarily _the_ Bitcoin blockchain. But one created along the same principles by election authorities.
I was thinking about my coffee.
"Scotty. Beam me to the finish line."
Music/podcasts are great for training but generally frowned upon in actual races,
It might be better to seperate the music from the other functions. Get something like an iPod Shuffle and do the rest with a GPS/monitor device. For a bit more bulk than a watch, a Garmin eTrex 30 will do GPS, altimiter and talk to an external heart rate monitor (and record your data as you go). I know some people who will cycle a course and download the elevation data into a programmable stationary cycle. The recorded data 'duplicates' the course elevation for trining purposes.
The battery life is about 25 hours.
Benelli Super 90
There's the target aquisition and tracking problem. That could be an issue at night when drones can fly GPS or inertial guidance (night/day doesn't matter to a drone).
Drugs, cigarettes, weapons, cell phones.
Something like this. Although the air marshals carry a P229 Sig Sauer chambered for .357 Sig rounds (a 10mm auto shell necked down to a .357 bullet). So, not really concerned with overpenetration or blowing out a window.
Are you sure about that?
This.
I've carried a Leatherman tool on myself aboard flights before 9/11 (on 9/9/01 actually).
So, let's allow passengers with concealed weapons permits to carry on board.