Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment No regulatory capture for you, DJI (Score 1) 75

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.

Comment Re:Dedicated patent courts. (Score 3, Informative) 55

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.

Comment Re:No, in reverse (Score 1, Troll) 269

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.

Comment Re:Conversely... (Score 1) 243

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.

Comment Re:Picking one at random (Score 1) 234

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.

Comment Picking one at random (Score 5, Informative) 234

The Professional Programmer

What is a professional programmer?

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 Top Deals

Every little picofarad has a nanohenry all its own. -- Don Vonada

Working...