Different people from different viewpoints are almost invariably GOOD for an organization. Those that don't have diversity tend to wither and die due to stagnation.
If they believed that were so, organizations which tout "diversity" wouldn't be so intolerant of diverse viewpoints (c.f. Mozilla, Grubhub)
The FAA has been amusing itself by passing regulations intended to keep drones on the ground to keep the skies clear for flying buses and FAA-licensed pilots; it sticks in the FAAs and licensed pilots' craws that any child can obtain a bit of floating latex (and especially mylar); drones piloted by ordinary humans who haven't spent years learning the proper radio calls and paperwork to file must drive them batty. Might matter for commercial drones; non-commercial ones are unpoliceable, just like those mylar balloons they like to report as "drones".
As for pedantry, it's law; it's supposed to be pedantic. If the regs meant any electrical system, it would say so; it's pretty clear about "engine-driven" electrical systems. That means that a drone with a battery-powered electrical system is not covered.
Programmers think that their jobs will always exist.. I think we've got another 20-25 years before the bulk of programming jobs have vaporised in the face of AI.
And another 5 years after that before the bulk of humans have been vaporized by the AI.
Nobody in their right is going to give the local cops HERF guns; they'll be shooting everyone and everything with them ("I saw a drone!") and causing all sorts of damage. The actual drones, of course, will be gone long before the cops show up.
you may have to serve as an apprentice (in my state, electricians serve a 5 year apprenticeship)
An electrician and an electrical engineer are rather different.
So whether you're an engineer or not depends on the state government, not a vendor or a school. This also provides more global skills.
Global? Ha. If you have a professional license it's good in one state. Other states _may_ provide reciprocity, or they may not. If the state you want to move to requires that your education took a slightly different course than it did, or had a different standard for professional supervision, you might be fucked.
When I was getting my degree (90's) the ACM wrote about the issue of whether software could truly be called "engineering" or not.
ACM broke with the IEEE over the issue of whether a professional engineering licensing program for software was appropriate; ACM felt it was not while IEEE felt it was.
A lot of P.E.s are certainly butthurt over the fact that others call themselves engineers without being P.E.s. Too bad on them; train drivers were called 'engineers' long before there was a P.E., and those who built and operated siege engines were 'engineers' long before that. I don't see why we should cede the term to Johnny-come-lately stick-in-the-mud State-worshipping credentialists like P.E.s
Genie's out of the bottle, and neither the FAA nor DJIs weak-sauce attempt to corner the market by suggesting the mandating of a technology they just happen to have ready in their back pocket (probably protected with some bogus patents) is going to stop it. Yeah, they can hit you with a jillion-dollar fine for operating your drone with an open-source controller, but that requires they catch you first, and the FAA lacks the manpower.
There's a huge difference between being the "de facto" standard due to rubberstamping in favor of the plaintiff (who usually gets to decide where they file their complains,) and being explicitly designed with the intent of treating cases fairly ie: not favoring the plaintiff by default.
Unfortunately, not really. Patent appeals are by design handled exclusively by the Court of Appeals for the Federal Circuit.... which results in them favoring a very expansive version of patent law even when SCOTUS tells them to cool it.
It's more like "halve the emissions", not "halve the energy". See, it's about trying to generate electricity for us to use, while reducing the byproducts that are bad for the environment.
Not fooling anyone; it's quite clear that many of the same people who want to cut CO2 emissions will fight tooth and nail against any large-scale energy project regardless of CO2 emissions. Nuclear produces waste, wind kills birds and requires ugly transmission lines, solar damages the delicate desert enviroment and increases the albedo of the planet, don't even f--ing think about hydro, etc.
Yesterday I bought some 1 x 6 treated boards and sawed them to length.
Yeah, about that. Those boards might have been made of the Fast-Gro (a trademark of the Brawndo corporation) variety of southern pine, a protected plant variant. Furthermore, that treatment process is patented (the EPA outlawed the public domain one). If this ruling stands, one or both rights-holders can insist that you use only their equipment to cut those boards to length. If you don't, your gate gets confiscated along with your house, sold to pay the penalties.
So yes.... you might get paid, but if you don't have enough of a passion to do what you get paid for
It is passion that is the mark of the amateur; the word is derived from the Latin for "love", after all.
To a professional, passion is dangerous, it leads to doing things that aren't remunerated.
then odds are going to be that you will be passed up for promotions
Ah, but promotions in this profession are a simple and spare thing. You work a few jobs, eventually you start calling yourself "Senior". After that, there's nowhere for a programmer to go and remain a programmer. You want to go beyond that, and you have to become a manager, or a lead, or an architect (God forbid!). Or you can go into business for yourself as a consultant, where you will have to be even more mercenary.
A professional programmer is someone who gets paid to do the job of programming.
Professional programmers take responsibility for their career, their estimates, their schedule commitments, their mistakes, and their workmanship. A professional programmer does not pass that responsibility off on others.
Sorry, bud, but professionals take responsibility for what they're paid to take responsibility for; no more and no less. And push responsibility off when appropriate too, like when their boss commits them to a schedule they can't make without compromising workmanship.
If you are a professional, then you are responsible for your own career. You are responsible for reading and learning. You are responsible for staying up-to-date with the industry and the technology. Too many programmers feel that it is their employer's job to train them. Sorry, this is just dead wrong. Do you think doctors behave that way?
Hell, yeah, they do. What do you think a resident is? Maybe the author is confused because after residency, many doctors are owners of their own practice, at which point they are not just professionals but business owners. Me, I draw a salary. If my training is going to benefit The Company, it's on The Company to provide it.
Professionals take responsibility for the code they write. They do not release code unless they know it works.
Again with the confusion between a professional and someone with independent authority. My code goes out when the boss says it goes out, ready or not.
Professionals are team players. They take responsibility for the output of the whole team, not just their own work.
Obviously not familiar with life in a corporation. Managers and leads take responsibility for the output of the whole team, when that output is good. When things are fucked up, THEN the programmers get the responsibility. Shit flows downhill, credit is taken upward.
Professionals do not tolerate big bug lists.
Professionals fix those bugs, and only those bugs, they're being paid to fix. The rest can sit in the issue tracker until doomsday. Ain't no point in getting the boss riled up over spending time fixing a minor floating point division error when you're supposed to be working on the shiny new feature.
Professionals do not make a mess. They take pride in their workmanship. They keep their code clean, well structured, and easy to read. They follow agreed upon standards and best practices. They never, ever rush.
A professional rushes when being paid to rush. A professional keeps the code clean when practical under the constraints of the job. If that means we're getting the code out on time only with a bunch of copypasta and a goto or two, that's how it's going.
Professionals get paid. If they have a rare combination of independent authority and a client with respect for them, maybe they can have other principles too. Otherwise, they write the code which gets them paid.
Slashdot Mirror
Helicopter, not plane. Not sure why, the things cost a fortune to run and are quite space limited, but it's always helicopters.
No, they searched the machines of the employees named. Presumably with their permission, since one of them -- Levandowski -- didn't co-operate.
So while other companies are actually developing self-driving cars, IBM is looking at what they'll need and throwing patent mines into their path.
How Brave New World.
If you lick a battery, it tastes sour. This is either a put-on, or an attempt to get published in the Annals of Improbable Research
If they believed that were so, organizations which tout "diversity" wouldn't be so intolerant of diverse viewpoints (c.f. Mozilla, Grubhub)
The FAA has been amusing itself by passing regulations intended to keep drones on the ground to keep the skies clear for flying buses and FAA-licensed pilots; it sticks in the FAAs and licensed pilots' craws that any child can obtain a bit of floating latex (and especially mylar); drones piloted by ordinary humans who haven't spent years learning the proper radio calls and paperwork to file must drive them batty. Might matter for commercial drones; non-commercial ones are unpoliceable, just like those mylar balloons they like to report as "drones".
As for pedantry, it's law; it's supposed to be pedantic. If the regs meant any electrical system, it would say so; it's pretty clear about "engine-driven" electrical systems. That means that a drone with a battery-powered electrical system is not covered.
And another 5 years after that before the bulk of humans have been vaporized by the AI.
It specifies an "engine-driven" electrical system. Most drones do not have an engine-driven electrical system.
Nobody in their right is going to give the local cops HERF guns; they'll be shooting everyone and everything with them ("I saw a drone!") and causing all sorts of damage. The actual drones, of course, will be gone long before the cops show up.
An electrician and an electrical engineer are rather different.
Global? Ha. If you have a professional license it's good in one state. Other states _may_ provide reciprocity, or they may not. If the state you want to move to requires that your education took a slightly different course than it did, or had a different standard for professional supervision, you might be fucked.
ACM broke with the IEEE over the issue of whether a professional engineering licensing program for software was appropriate; ACM felt it was not while IEEE felt it was.
A lot of P.E.s are certainly butthurt over the fact that others call themselves engineers without being P.E.s. Too bad on them; train drivers were called 'engineers' long before there was a P.E., and those who built and operated siege engines were 'engineers' long before that. I don't see why we should cede the term to Johnny-come-lately stick-in-the-mud State-worshipping credentialists like P.E.s
Airstrip One was always part of Oceania, not Eurasia.
Genie's out of the bottle, and neither the FAA nor DJIs weak-sauce attempt to corner the market by suggesting the mandating of a technology they just happen to have ready in their back pocket (probably protected with some bogus patents) is going to stop it. Yeah, they can hit you with a jillion-dollar fine for operating your drone with an open-source controller, but that requires they catch you first, and the FAA lacks the manpower.
HFS+ was introduced in MacOS 8.1 (a point release of Mac OS 8). HFS in System 2.1 (following 2.0).
Unfortunately, not really. Patent appeals are by design handled exclusively by the Court of Appeals for the Federal Circuit.... which results in them favoring a very expansive version of patent law even when SCOTUS tells them to cool it.
God damn, it's nice that there's one thing on the Internet that doesn't change.
Yeah, which would you rather have, a nice juicy steak or 10 times the number of neighbors?
Not fooling anyone; it's quite clear that many of the same people who want to cut CO2 emissions will fight tooth and nail against any large-scale energy project regardless of CO2 emissions. Nuclear produces waste, wind kills birds and requires ugly transmission lines, solar damages the delicate desert enviroment and increases the albedo of the planet, don't even f--ing think about hydro, etc.
Moore's law meant you got MORE. This means you get less. Half the energy every decade. This is a prescription for misery and starvation.
One can hope. Watch for executives leaving, especially executives who would have that kind of signing authority.
Yeah, about that. Those boards might have been made of the Fast-Gro (a trademark of the Brawndo corporation) variety of southern pine, a protected plant variant. Furthermore, that treatment process is patented (the EPA outlawed the public domain one). If this ruling stands, one or both rights-holders can insist that you use only their equipment to cut those boards to length. If you don't, your gate gets confiscated along with your house, sold to pay the penalties.
That's JUST what an avatar for the runner of the simulation would say!
Cooling of the past via statistical tricks?
It is passion that is the mark of the amateur; the word is derived from the Latin for "love", after all.
To a professional, passion is dangerous, it leads to doing things that aren't remunerated.
Ah, but promotions in this profession are a simple and spare thing. You work a few jobs, eventually you start calling yourself "Senior". After that, there's nowhere for a programmer to go and remain a programmer. You want to go beyond that, and you have to become a manager, or a lead, or an architect (God forbid!). Or you can go into business for yourself as a consultant, where you will have to be even more mercenary.
A professional programmer is someone who gets paid to do the job of programming.
Sorry, bud, but professionals take responsibility for what they're paid to take responsibility for; no more and no less. And push responsibility off when appropriate too, like when their boss commits them to a schedule they can't make without compromising workmanship.
Hell, yeah, they do. What do you think a resident is? Maybe the author is confused because after residency, many doctors are owners of their own practice, at which point they are not just professionals but business owners. Me, I draw a salary. If my training is going to benefit The Company, it's on The Company to provide it.
Again with the confusion between a professional and someone with independent authority. My code goes out when the boss says it goes out, ready or not.
Obviously not familiar with life in a corporation. Managers and leads take responsibility for the output of the whole team, when that output is good. When things are fucked up, THEN the programmers get the responsibility. Shit flows downhill, credit is taken upward.
Professionals fix those bugs, and only those bugs, they're being paid to fix. The rest can sit in the issue tracker until doomsday. Ain't no point in getting the boss riled up over spending time fixing a minor floating point division error when you're supposed to be working on the shiny new feature.
A professional rushes when being paid to rush. A professional keeps the code clean when practical under the constraints of the job. If that means we're getting the code out on time only with a bunch of copypasta and a goto or two, that's how it's going.
Professionals get paid. If they have a rare combination of independent authority and a client with respect for them, maybe they can have other principles too. Otherwise, they write the code which gets them paid.