6 ms·
Were we ever considered professionals? There's no test - all you have to do to be a software developer is declare yourself to be one. There's no overarching pro
by pessimizer 13y ago
Were we ever considered professionals? There's no test - all you have to do to be a software developer is declare yourself to be one. There's no overarching professional organization or boards, therefore incompetents aren't de-certified and national lobbying isn't coherent.
In fact, the largest companies that we work for are frequently lobbying for things that programmers don't support, or actively damage our interests in relation to management.
We're also generally professional middle-class conservative enough that we're anti-union in a way that only people who are members of professional organizations that are at least 100 years old can afford to be. For doctors and lawyers it's easy to ignore cognitive dissonance because the freebies they get are so baked into government that it's hard to remember that people actually had to make a conscious effort to make that happen. There's no reason for programmers to be so complacent.
The transistor isn't even as old as the National Association of Realtors. People in real estate have more clout, baked in advantage, and respect as a member of a profession than anybody can be expected to get by calling themselves a programmer. At least they have to take a test.
- Havoc 13y ago>the freebies they get are so baked into government What exactly do you understand under freebies [for 100y+ prof org members]? Interesting point about the older prof members being both anti-union and but joining a prof body. I reckon the two have different functions though. e.g. In my case the only thing I hear from my prof org is messages with a "comply or else" tone. Sure they do set minimum salaries for apprenticeships, but those are so far below market rate that its does even matter. A union in contrast would fit for better work conditions, better pay, better benefits etc. The only benefit I see is accreditation (admittedly a large benefit)...but that is hardly a freebie (took blood, sweat & many tears).
- pessimizer 13y ago>What exactly do you understand under freebies [for 100y+ prof org members]? Doctors, Lawyers, Realtors, etc. have written 90% of the state laws that they are governed under, and most of the federal ones. They've protected themselves against foreign competition, and shielded themselves against liability.
- rayiner 13y agoWithout necessarily disagreeing with your point, it's interesting to note that software developers bear almost zero liability in practice for all the buggy software they write, while even big name law firms get sued, and lose, regularly on malpractice claims. If Microsoft was as "protected" from malpractice as lawyers are, they would've been sued out of existence for Windows 95/98/ME.
- pessimizer 13y agoOne of the benefits of being unprofessional, I guess, is that the products of our labor are generally considered products of the corporation we work for rather than us as individuals. Google, SAP, etc. get sued all the time, though.
- rayiner 13y agoGoogle, SAP, etc, get sued for things like breach of contract, patent infringement, etc. A lawyer or doctor can get sued for his or her work not meeting the expected standard. Imagine the following bug: a variable can take on values of RED, GREEN, and BLUE. You write a switch statement that fails to consider BLUE. Your product crashes, causing your user $5 million in business losses. You get sued for software malpractice, for failure to consider an obvious alternative case.
- pessimizer 13y agoPerfect case for how professionalism protects clients. We'd all have to carry insurance for that.
- rayiner 13y agoWell I wasn't really suggesting it as a good thing necessarily. I like the spirit that ethical/competency self-regulation instills in the legal profession, but I'm not sure whether the ultimate market impact is a good thing or not. On one hand, I think the financial industry has suffered from a lack of such regulation (e.g. Goldman advising clients to buy certain products while taking an adverse position themselves). On the other hand, the potential liability and need for insurance creates barriers to entry, driving up prices. Given the staggering potential losses from software, professional malpractice insurance probably wouldn't be cheap. But on the third, alien, hand, I think licensure also has a downward effect on the cost of legal services, by making lawyers more fungible than they would otherwise be (in the absence of licensure, the market might come to rely on an even rarer signal of credibility). The economic dynamics of licensed professions are a bit more complex than either side of the "developers should be professionals" debate really appreciates.
- Mvandenbergh 13y ago>The only benefit I see is accreditation (admittedly a large benefit)...but that is hardly a freebie (took blood, sweat & many tears). Sure, that's by the design of your fellow professionals. It's part of the mechanism for protecting the wages of fully qualified professionals. Unions are often happy enough with much lower apprenticeship wages as well by the way. The two biggest freebies are also the two traditional markers of the professions: -Self regulation: most misconduct is dealt with by peers under rules set by those peers -Protected entry: lawyers and doctors control how many people can enter those professions and who can call themselves a lawyer or a doctor.
- walshemj 13y agoThe BMA and RCN do act in the capacity of a trade union in a lot of ways though.
- potatolicious 13y ago> "e.g. In my case the only thing I hear from my prof org is messages with a "comply or else" tone." That is one of the primary functions of professional organizations. The idea is that you'd rather self-regulate than have the government all up in your business. Disputes and claims of impropriety can avoid the courts (and the public limelight) and be resolved internally. The consequence of that is that you actually have to self-regulate, and that your enforcement arm needs to have teeth. This is how it works in traditional engineering. Most engineering misconduct - short of the catastrophic stuff that makes the evening news - is dealt with internally. For the most part they do a good job of it, which is why they've been able to avoid being outright regulated deeply by the government.
- walshemj 13y agoAnd what has the IEE done to raise the status for Engineers in the UK in last 100 years.
- BrownBuffalo 13y agoRIGHT?!?
- arethuza 13y agoDon't you mean the IEE (now the IET) rather than the IEEE? http://en.wikipedia.org/wiki/Institution_of_Electrical_Engineers http://en.wikipedia.org/wiki/Institution_of_Electrical_Engin...
- walshemj 13y agoOops yes I was thinking of the pre amalgamation set up - I used to be a Junior Member of the Mech engineers
- BrownBuffalo 13y agoActually there is. If you are a software developer, you are skill laborer. If you are software engineer - you have the PE / FE exams. In some states its even illegal to call yourself a softare engineer (or [insert word here] engineer, without having an "engineering" degree. Secondly, the major problem to start out with is the proper business definitions / rules for which the software is designed for. Because software devs/*neers have a more "generalized" tool building education (either/or work experience / degree education), the understsanding has to come from both sides - we explore the capabilities and compare that to the process you are trying to map for your industry. But I digress ...
- pessimizer 13y agoThat's an example of the professional clout of engineers, not programmers.
- Mvandenbergh 13y agoThe issue is that you don't need to be chartered professional software engineer to get virtually any programming job. That isn't true for other engineering professions. Most civil engineers are PEs and they often have to be to do their jobs legally. Mechanical engineers are often PEs. Electrical engineers doing electronics often don't bother (as it isn't legally required for most work) but EEs doing line-voltage and above design work usually have to be.
- walshemj 13y agoNot really I worked at a top 5 civil consultancy and the majority of engineers where not chartered it takes quite a few years of professional work to achieve that status. and its more about "who you know not what you know" to quote my dad
- Mvandenbergh 13y agoSure, but those people are still working towards accreditation, they're part of that system in a way that most software engineers are not.
- tjr 13y agoWere we ever considered professionals? Not officially, no. I've always liked this line of thinking, though: http://philip.greenspun.com/ancient-history/professionalism-for-software-engineers http://philip.greenspun.com/ancient-history/professionalism-...
- walshemj 13y agoThat's "engineering" language for you :-)
- netcan 13y agoThere are a bunch of reasons why strict membership would be problematic. First is the level of informal training that forms the basis for a lot of (good and bad) software developer's knowledge/ability. Certification favors some approved educational requirements. Second is the fact that professional certification is at its strongest when membership/non membership is a pretty decent indicator of competence. IE a certified plumber will instal toilets that consistently flush downward. Will a certified software developer be more likely to improve a client's chances that a project will be delivered and solve the problem its trying to solve? That said, I can't see a strong objection to a voluntary organization recruiting members and seeing if they can add some value somewhere. Hopefully they don't try to keep all the compilers to themselves.
- pessimizer 13y agoRealtors certify through a moral test rather than a professional one. The test is simply a way to define a minimum standard, and a way to expel immoral incompetents. http://www.realtor.com/advice/what-the-realtor-code-of-ethics-means-to-you/ http://www.realtor.com/advice/what-the-realtor-code-of-ethic... Realtors established a code of ethics, and made one of the articles in the code to be competent and knowledgeable, and if incapable of a job to turn it down or refer it to someone who can do it. They enforce this with precedents establishing minimal expectations, which are as precedents are flexible as times change. If your organization actively enforced a 'Programmer code of ethics', and programmers were facing expulsion for being fuckups, I think that's "likely to improve a client's chances that a project will be delivered and solve the problem its trying to solve." The ultimate problem is that expulsion has to be a real punishment. You can do that through changing laws to make membership actually not voluntary, though it may still be nominally voluntary (like doctors, and lawyers), or to distribute resources for work through the organization (like realtors), or to simply refuse to work with organizations that use people who don't belong to the organization (like actors and stagecraft unions, for example) and to be large enough for that to make a difference.
- maratd 13y ago> There's no overarching professional organization or boards, therefore incompetents aren't de-certified and national lobbying isn't coherent. Incompetents are rarely de-certified in professions that have what are effectively guilds. How nutty do you have to be to appreciate a holdover from the middle ages? In fact, it is usually the incompetents who seek the protection of guilds and unions. Without them, where would the air of competence come from? They might actually be asked ... gasp ... to perform some task to prove their competence! When was the last time you asked your lawyer to perform a "legal test"? We get asked to do small code tests and projects to prove our competence all the time. > There's no test - all you have to do to be a software developer is declare yourself to be one. Really? No tests? Because there is no bullshit-institutionalized-social-proof crap, we are asked to take a test and prove our mettle before being hired for every job. A genuine filter to get rid of the incompetents. I am thankful every day that I'm not part of a regulated industry.
- pessimizer 13y agoI don't know what you do for a living, but as a programmer, I meet incompetents who should be expelled from the profession all of the time. Aside from incompetence, I don't want to share a profession with programmers who would help create a surveillance state for the NSA, any more than the medical profession should tolerate doctors who work for torturers. The question is about programmers being considered professionals, though, not what I'd prefer. I'm happy with my check and my title.
- maratd 13y agoMy point wasn't that there are no incompetent programmers. There are plenty. My point was that in our profession, and it is a profession, it is much more difficult to be incompetent. As a consequence, there are fewer incompetents than in other professions. In regulated professions, once you get through the door and get certified/licensed/whatever you can then use that as a badge of competency to get work. You can't do that with software development. Nobody cares what certification or degree you have. They want to know if you can code. How wonderful is that?
- bmj 13y agoThere's no test - all you have to do to be a software developer is declare yourself to be one. There's no overarching professional organization or boards, therefore incompetents aren't de-certified and national lobbying isn't coherent. And how does testing work? Do you do language-specific tests? Or general CS knowledge tests? And how do CS-knowledge tests apply to HTML/CSS slingers? Or are they not "programmers?" And if you certify by language, what does a company do when it wants to use a different, perhaps more applicable language for a product? Must all their devs be certified first? And what would this do for language development? Would anyone adopt new languages (or even variants) knowing that there are now institutional barriers?
- potatolicious 13y agoNone of the above. If you look at professional self-regulation in traditional engineering, the focus isn't on competence. There is usually a very mild verification of basic fundamentals. In our world that'd probably translate into "what is an array"? The bulk of accreditation/certification in this context is not a guarantee of your competence, but a guarantee of your professionalism, and to set you up in a system where unprofessional conduct can be punished, and integrity enforced. The intent of this sort of regulation isn't to make sure everyone is an amazing programmer, but rather that they will operate above-board, be reliable and trustworthy, and recognize the limitations of their own abilities. The market, via salaries and benefits, will sort out people by ability. The intent here is instead to establish safeties for the demand-side such that they can hire with relative peace of mind, knowing that even if the person sucks at programming, they won't abscond with your codebase, engage in conflicts of interest, etc. And if they do, that there is a strong enough enforcement arm that provides both deterrence and retribution. It is also intended to protect practitioners by guaranteeing that the people investigating and hearing claims of malfeasance are actually skilled enough in the craft to fairly evaluate the claims.