Slashdot Mirror


The Rising Power of Developers

msmoriarty writes "Google's Don Dodge, GitHub's Tom Preston-Werner, New Relic's Lew Cirne and others recently got together in San Francisco on a panel called 'The Developer is King: The Power Behind the Throne.' According to coverage of the event, the panelists all agreed that programmers — both independent ones and those employed by companies — have more power, and thus opportunities, than ever. Even the marketing power of developers was acknowledged: 'The only way to convince a developer is by giving them a demo and showing them how it's better,' said Preston-Werner. 'The beauty is, you plant these seeds around the world, and those people will evangelize it for you. Because another thing that developers are great at is telling other developers what works for them.'"

36 of 122 comments (clear)

  1. Pat on the back by Noughmad · · Score: 4, Insightful

    Some rich guys got together, told themselves how great they are and how they deserve to be rich. News at 11.

    --
    PlusFive Slashdot reader for Android. Can post comments.
    1. Re:Pat on the back by benmk · · Score: 2

      So, no need to watch the news at 11 anymore. Well then, just do some coding...

    2. Re:Pat on the back by JaredOfEuropa · · Score: 3, Interesting

      Good point, but the problem is that very few people see the width of that spectrum. Sucks if you're a head chef but your boss can't really see how you're different from the burger flipper, except that you seem to flip more or bigger burgers.

      That's why I call bollocks on TFA. VCs favour developer-founders now? It might be a good move but then again, it might not, and next month they'll favour people with neatly trimmed hair, just like last month they were favouring people with business experience. As for programmers, their power has declined. A long time ago (in tech-land terms), programming was a respected profession, not just amongst peers but also by the general public, and by those programmers' employers. That had already ended when I got into the game, but even back then, programmers did have a significant amount of influence on the design and parameters of the program. As a programmer I got to join meetings on product and service design with the CTO and marketing manager of a large mobile telco. Small projects were generally left to be managed by team leads who were also programmers. And project managers of larger projects often deferred to his developers.

      Today, most larger corporations keep their programmers in the basement. The aspect of the job that involved contact with clients, management and business representatives is now handled by sales reps, project managers and business analysts. Most of whom have a very weak grasp of technology, I might add. The chasm between tech and business hasn't widened, but the bridges have gone and we're reduced to flinging memos across the gap. On top of that, now we're seeing heavy compartimentalisation of the work, by defining standards and procedures that attempt to turn creativity and flexibility into predictable monkey work. Now, standards and procedures aren't necessarily bad, and the field of software development can do with some professionalisation, but what's being introduced now moves us in the wrong direction. Even the master coders' jobs are being reduced to burger flipping, or at least managers are trying to.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    3. Re:Pat on the back by johnjaydk · · Score: 2

      Can we please put developers in the back seat as run of the mill production workers like they belong. I respect a minority of software architects, but plain jane code toads need to be getting the treatment and pay of the few steps above fry cook that they are.

      Giving developers that kind of treatment causes a very low productivity and little attachment to the company. That's going to hurt your bottom line. But hey, it's your bottom line. I'm not going to complain the karmic blowback that's going to hit you.

      BTW. Welcome to the select few i my foe's list.

      --
      TCAP-Abort
    4. Re:Pat on the back by RabidReindeer · · Score: 2

      Can we please put developers in the back seat as run of the mill production workers like they belong. I respect a minority of software architects, but plain jane code toads need to be getting the treatment and pay of the few steps above fry cook that they are.

      The way most companies work aritechture is an underfunded joke and each and every decent programmer is their own architect. The REALLY good ones play well with others AND do their own brilliant designs.

      If the developers you are employing are a step above fry cooks, please tell me which company you work for so I can avoid having anything to do with that disaster waiting to happen.

      The joke in my town is that "architect" is the title of the person who ships the work to the offshore coders.

  2. it might be true, but not very convincing panel by Trepidity · · Score: 4, Insightful

    A group of successful developers get together on a panel and, surprisingly, everyone on the panel agrees that developers are very important and goin' places in the world.

    1. Re:it might be true, but not very convincing panel by Darinbob · · Score: 5, Insightful

      Meanwhile, you get back to work and tell the boss that the new product feature is a bad idea, and you get told to shut up and keep rowing.

    2. Re:it might be true, but not very convincing panel by CrankyFool · · Score: 2

      It depends on the place you are. Perhaps, more generally, it's better to say that in some companies developers have a lot of power, whereas in some companies they don't. If you don't like how developers are treated in your company, have you considered your options?

      I'm an engineering managers, with developers reporting to me. They figure out where the product needs to be going. I provide input, which they often, but not always, listen to. Generally, they listen to our customers (internal people) more than they listen to me. Seems like the right approach for us.

    3. Re:it might be true, but not very convincing panel by terryducks · · Score: 2

      ... keep rowing

      the good new is that there will be extra rations

      the bad news is that the fat bitch will want to water ski tonight.

    4. Re:it might be true, but not very convincing panel by StripedCow · · Score: 3, Interesting

      Actually, when I read the headline, I was hoping this article was about programmers starting a union, to collectively fight things such as diverging programming ecosystems, software patent abuse, deliberately broken/abandoned APIs, walled API gardens, etcetera.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
  3. Power? For who? by djupedal · · Score: 4, Interesting

    This is all about marketing power, and using devs as mouthpieces. Devs are always either agreeing or arguing, with the new ones either lapping up anything the older ones say or dissing them as crotchety and set in their ways. The only selling I see going on is on what resources to use and which to ignore, and there are always a basket of opinions going in different directions depending on which site you're on at the moment. If someone can find a way to milk them as a group, beyond, you know...developing stuff, then go for it, but to say they are king makers is a bit of a virtual stretch. Any marketer will see them as just another group.

    1. Re:Power? For who? by fat_mike · · Score: 4, Funny

      No offense but the first rule of marketing for a software company is "Hide the damn developers and for the love of everything good and sweet do not let them talk to stockholders or customers!"

    2. Re:Power? For who? by Opportunist · · Score: 3, Informative

      Yup. I noticed that devs tend to be truthful. Really insane bunch of geeks.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  4. Ready for an H-1B increase? by ebno-10db · · Score: 4, Insightful

    programmers — both independent ones and those employed by companies — have more power, and thus opportunities, than ever

    Sounds like part of a campaign for an H-1B quota increase.

  5. Yep by ShooterNeo · · Score: 5, Funny

    In the long run (read : I mean the next 30 years), every job in existence has a programmer involved.

    Manual Labor? In the long run, it'll be robots that do nearly all of it, and software is the only real obstacle that stops us from automating more tasks.

    Manufacturing? Software problem. Healthcare? Most of a doctor's thinking could be automated with existing software techniques. (sure, not the physical procedures part, but that's only a portion)

    Of course, in the LONG, LONG run, someone will advance the art of software to the point that we have software that can write itself, and then we're all out of work...

    1. Re:Yep by Macchendra · · Score: 2

      We are about 30 years out from recursively self-improved artificial intelligence, which is about 0.0001 years away from Skynet/The Borg/Agent Smith/etc. Hopefully by then we will have perfected Stupidamin(tm): the supplement that keeps you comfortable while watching television.

    2. Re:Yep by Livius · · Score: 3, Insightful

      Luckily in 20 years it will still be 30 years away, which will give us a little time.

  6. Re:Lies by spiffmastercow · · Score: 5, Insightful

    I have never met a competent developer who had trouble finding work.

    I HAVE met incompetent out-of-touch, burnt-out, full-of-themselves developers who can't find work. It's this second kind that think they're good but are not and who should be in another field.

    As far as finding work goes, you're probably correct. I have, however, met a fairly large number of good developers who are 10x more productive than an average programmer, but have difficulty getting paid what they're worth.

  7. We'll screw it up by Anonymous Coward · · Score: 2, Insightful

    We (software engineers and developers) are the dumbest group of skilled professionals in the history of skilled trades. No other field, no other economic opportunity has been so badly squandered as the field of software development -- ever.

    Compare software engineers to doctors or lawyers. Both doctor's and lawyers have to pass exams. They are certified by boards of other professionals. If a doctor or lawyer screws up badly enough they lose their right to be a doctor or lawyer. Not software engineers. When a software engineer writes terrible code they are not disbarred and the screw up reflects poorly on the trade in general. No wonder people don't respect our field -- we don't respect it ourselves.

    We've taken the secrets and tools of our trade, open sourced them, and created legions of arm chair professionals around the world who not only reflect badly upon our trade but undermine the very vitality of it. Why spend thousands of dollars to get a degree to compete on Craigslist for $6 and hour? How can we expect our customers to hire good developers when we don't give them any metric to use to rate good developers?

    1. Re:We'll screw it up by phantomfive · · Score: 3, Insightful

      No wonder people don't respect our field -- we don't respect it ourselves. ... We've taken the secrets and tools of our trade, open sourced them

      I definitely don't respect programmers who think they need to keep their source hidden in order to stay competitive.

      --
      "First they came for the slanderers and i said nothing."
    2. Re:We'll screw it up by Zenin · · Score: 5, Insightful

      Here's the problem: Most all of what makes a good lawyer or doctor isn't at all about finding creative, novel ways to solve problems. Much the opposite in fact; Creative application of law or medicine is most likely to get you disbarred or thrown in jail. It's much easier to create a quantifiable exam when the subject matter is so well defined and creativity is shunned.

      In software however, it's completely the opposite. Creative, novel application of existing technology and/or the invention of entirely new technology, is a good software developer's bread and butter. It's a big part of the essence of what makes them a good developer rather then a coding drone.

      So how do you create an exam to quantify a good developer? By the very nature of what you're looking for the only "right" answers are "wrong" ones. But which wrong answer is right? That's completely subjective in an exam setting, however in the real world it's much easier to quantify: Your shit works and works well or it doesn't.

      --
      My /. uid is better then your /. uid
    3. Re:We'll screw it up by Anonymous Coward · · Score: 2, Insightful

      That's funny. I think most developers are held in high regard because they have NOT built a mote around the profession like doctors and lawyers.

      I've seen too much doctoring done by nurses, too much law done by paralegals to have much respect for either profession. Then of course there's the whole, "Why don't you take this drug, you know the one with the same logo as the pen you used to sign the form?". This definitely happened to me. The drug? Celebrex, which wasn't even indicated for my condition. I said "no", because even then I was deeply suspicious of the way the drugs are marketed and the way the doctors were pushing them. Surprise, surprise, when this class of drugs was pulled for a while and brought back with a bunch of warnings.

      And then we have the lawyers, writing the laws that become ever more complex so... you need a lawyer.

      If anything, Open Source is a problem because it tends to require a developer for you to get mods in place. If anything, OS/FS makes software more like law, not less. At least there isn't broad consensus among all developers that we have to develop under OS/FS if we don't want to. Both models are allowed to compete, and under some circumstances proprietary wins and other some circumstances it doesn't.

      Professional organization, cert body? No thanks.

  8. Reality by Baldrson · · Score: 4, Interesting
    My personal dilemma is that one of the few ways I can capitalize on my 40 years experience in computer programming is to make money training young people to go into the software profession.

    Its hard to explain to folks who see my resume and employment status why I refuse to accept money to train train local young people.

    First of all people aren't used to people with ethics. So they don't understand why I wouldn't want to take money from kids by leading them into pauperism.

    Secondly they've been led to believe that domestic programmers with equal skills have an equal shot at the high income positions that are going to foreign aggressors. Its one of those things that's just too depressing to admit to one's self about the horror of the government's oppression of the citizens. This is especially true in rural areas where almost every family has a young man who has served in the military and either killed, or been indoctrinated that is is ok to kill for the government (if they, themselves haven't been permanently disabled if not killed).

  9. all the power? by alienzed · · Score: 4, Funny

    I for one welcome our new developer overlords...

    --
    Never say never. Ah!! I did it again!
  10. Re:Lies by phantomfive · · Score: 2

    To find work, you need a skill: You need to be able to convince people that you can provide a level of value for the pay.

    This is easy if you just want average-skilled developer work, all you need to do is have a degree/work experience/answer interview questions. It's a LOT harder if you want to convince people to pay you for significantly above average work, but that is the skill you need if you want that kind of pay.

    --
    "First they came for the slanderers and i said nothing."
  11. Re:Mod parent up by Anonymous Coward · · Score: 5, Insightful

    Opposite anecdote: I live in a major city on the West coast of the U.S., and I've never had a period of the last 7 years where I couldn't get a six figure offer when I wanted a new job. And I didn't even have to move.

    The lesson from your travels isn't that being a computer programmer is a bad gig. It's that you shouldn't move to a place where there is only one job. Move to a major metropolitan area, and you can earn a lot of money with virtually zero unemployment in the field.

  12. Re:Lies by Anonymous Coward · · Score: 2, Informative

    To find work, you need to be in the right city, and have the right credentials, which are typically inflated since they'd rather outsource the work anyway.. Otherwise, do you want fries with that?

  13. Re:Lies by Darinbob · · Score: 5, Insightful

    I have been out of work in the past for nearly a year. Lots of people claiming that they wanted to hire me, if only they had the budget. When the economy is bad and there are no job openings, it doesn't matter how competent you are. Maybe a lot of these new people haven't really been in a bad economy or downturn except the current one. Also the fads comd and go, if the current fad is web sites with scripting language of the day, and you don't know web stuff, then all those jobs pass you by no matter how good a programmer you are.

    Some of the people that do the best with getting jobs are the dabblers, quickly learning the rudiments of something and then moving on in a few years when fashions change; client/server turns into palm pilot apps turns into web design turns into mobile apps, etc.

    Also very important to finding a job, is to not be geeky and nerdy. You need people skills and that is not easy to learn for the borderline autism spectrum people who are great coders and hardware designers and mathematicians. You have to learn to NOT be yourself in an interview.

  14. Re:Lies by Anonymous Coward · · Score: 2, Informative

    I have never met a competent developer who had trouble finding work. I HAVE met incompetent out-of-touch, burnt-out, full-of-themselves developers who can't find work. It's this second kind that think they're good but are not and who should be in another field.

    By "burnt-out", of course, you mean "old". Try getting a job when you're over 50. It almost doesn't matter how good you are, the resumes get dumped automatically if you say your college degree is from the 70's.

  15. What an empty fluff piece by msobkow · · Score: 4, Informative

    Not one example of developers succeeding or what they might have done to stand out in a sea of offshore contractors, but a bunch of self-congratulatory pap about how successful their own businesses are. And not ONE developer in the panel -- all pompous management taking the credit for themselves.

    --
    I do not fail; I succeed at finding out what does not work.
  16. Re:Lies by LordLucless · · Score: 2

    Also the fads comd and go, if the current fad is web sites with scripting language of the day, and you don't know web stuff, then all those jobs pass you by no matter how good a programmer you are.

    Some of the people that do the best with getting jobs are the dabblers, quickly learning the rudiments of something and then moving on in a few years when fashions change; client/server turns into palm pilot apps turns into web design turns into mobile apps, etc.

    Yes, people who never believed this new-fangled interweb "fad" was going anywhere, or never bothered learning any new technology after they left tertiary education because gosh darn it if C was good enough for Kernighan, it should be good enough for everyone - they might find it hard to get a job.

    Lawyers need to keep up-to-date on precedent, accountants need to know the latest tax changes, and doctors need to follow the latest developments in medicine. A developer needs to keep up with the changing nature of technology.

    --
    Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
  17. Yup. Developers are KING by Anonymous Coward · · Score: 2, Insightful

    ...right after

    1) Shareholders (reason why we're in business)
    2) Customers (who pays the bills?)
    3) Salespeople (who brings in the customers?)
    4) Top management (whose vision makes the difference between a big success and an also-ran?)
    5) Marketing (who identifies and attracts the customers?)
    6) Finance and accounting (who brings in investments and manages the cash so we can stay in business?)
    7) Lobbyists (who ensures that the government doesn't pass taxes and other legislation that would interfere with our business plans?)
    8) Press relations (who gets the word out to Wall Street so we can attract investment?)
    9) Recent college graduates (who will provide the 'fresh blood' and intimate knowledge of technological trends that will carry us into the future?)
    10) Offshore developers (who makes it possible to keep costs down so that #1-9 can be satisfied?) ....

  18. Re:Microsoft is dead by serviscope_minor · · Score: 2

    If it's the article I think you're talking about it was spot on, but you've misunderstood it.

    He never claimed microsoft was dead as in about to go out of business. He claimed that the big bad microsoft, a threat to the entire industry was dead. He was right. Perhaps you don't remember the world from back in the 90s ad the wake of destruction microsoft left in its path. The big fear of almost any software company was that microsoft woule enter the area and destroy them.

    I doubt github has ever had such a fear because that microsoft has died thankfully.

    If you speak to old timers, they'll tell you of the days when IBM left fear and destruction in its wake and had the industry in a death like strangle hold. That IBM is dead too, even though they're pulling in $100bn in revenue.

    Neither microsoft nor IBM have the industry dominance that they used to.

    --
    SJW n. One who posts facts.
  19. Re:Lies by cascadingstylesheet · · Score: 2

    Also very important to finding a job, is to not be geeky and nerdy.

    Yep.

    And it's not just for the interview. Unless you are a code monkey working robotic-like to the requirements that someone else makes for you, you need to have people skills for the job.

    You are probably not such a good coder if you don't have people skills. Just like it's hard to be "good" in bed if you are the only one there ...

  20. Re:Lies by narcc · · Score: 2

    I'm not sure why you're comparing RoR and NodeJS to PHP and Java, so the following might feel a bit confused. This is my take.

    The RoR fad is over and Ruby is starting to fall in popularity, so I don't expect to see it pass PHP (which, despite the hate, is actually growing).

    The NodeJS fad is just beginning. I'm not comfortable making any predictions about it just yet, though I suspect it won't gain much ground in the near-term, for practical reasons. JavaScript, on the other hand, isn't going anywhere anytime soon. It seems to get more important every year.

    Java is essentially dead on the browser. While it has a nice niche on the server, it's not really a significant player. Under Oracle, the best I can say is that its future is uncertain. Still, I wouldn't worry about starting a new Java project. If it's dying, it's got a lot of time to recover.

    Anyhow, what I see isn't a lot of instability and change, but a rather stable and safe set of languages for the web.

    PHP is practically ubiquitous, and owns quite a bit of the web (~80%). With lots of companies deeply invested in PHP for both public-facing sites and internal intranet apps, it's not going away any time soon. That makes it a very safe choice for new projects.

    I don't think I need to explain why JavaScript isn't going anywhere. Love it or hate it, it's pretty much your only option. Java applets aren't coming back. While Flash is going to hang on for years, it's essentially dead and thus unsuitable for new projects. You're ultimately left with just two safe choices on the browser: "use JavaScript" or "don't use anything at all".

    Looking back 10 years, things are basically the same. PHP was a smart choice for new projects, and JavaScript was still your only real choice on the browser -- though "nothing at all" was probably the smarter way to go at the time. (That's a long time. Think how much changed from 1993-2003 vs 2003-2013.)

    So I'm just not seeing that "languages used to program on the web are changing all the time" like the parent asserts. What I've seen are a few of fads come and go, each failing to gain against a now near standard set of tools.

    If "keeping current" means jumping on the latest bandwagon, count me out. I'll happily play with new things as they appear, but that's just for fun. I'd have to be crazy to make any sort of serious investment in what is very likely going to be the next passing fad. That said, I'll happily agree with you that new fads on the web appear infrequently enough that keeping up isn't difficult at all.

  21. Re:Lies by RabidReindeer · · Score: 2

    I have never met a competent developer who had trouble finding work.

    I HAVE met incompetent out-of-touch, burnt-out, full-of-themselves developers who can't find work. It's this second kind that think they're good but are not and who should be in another field.

    So you're like 18, or something?

    From mid-2001 to the same time in 2003 I spent more time not working than working. Headhunters all ran and hid. Before that, I had been part of the OS support team on one of the larger mainframes in town, solely responsible for several mission-critical products, then a developer for software for various different platforms. I was an early adopter of both C++ and Java, worked with J2EE before JSPs had been invented. I actually developed and brought one of the very first C++ compiler systems to the PC market.

    These days, I have clients who are quite happy with my ability to resolve thorny technical issues and keep their business prosperous and growing.

    But there have been fat times and there have been lean times. Be grateful if you haven't experienced the lean ones. Or if you have the people skills to keep Management loving you when they start kicking people with demonstrated abilities out on the street.